PRs for manpage 'rtadvd(8)'
This is an experimental report containing PRs for manpage 'rtadvd(8)' as of Fri May 30 07:39:13 2014 UTC. See notes.
PRs for manpage 'rtadvd(8)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2014/04/12 | bin/188510 | [patch] rtadvd(8): "rtadvctl show" crashes on BeagleBone Black due to unaligned access | |
| o | 2014/03/24 | bin/187899 | rtadvd(8) fills syslog with unneeded error messages | |
| o | 2013/07/24 | bin/180818 | [patch] rtadvd(8): rtadvd generates warnings when using in dhcp-pd enviroment | |
| o | 2012/11/28 | bin/173969 | rtadvd(8): sendd does not work | |
| o | 2012/03/06 | bin/165783 | hrs | rtadvd(8) eats 100% cpu |
| o | 2010/12/08 | bin/152928 | hrs | [patch] rtadvd(8) don't send RA on i/f that's down |
| f | 2010/11/21 | bin/152458 | hrs | rtadvd(8) needs to allow RA without a prefix info option |
Notes
GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.