PRs for manpage 'syslogd(8)'
This is an experimental report containing PRs for manpage 'syslogd(8)' as of Fri May 30 07:39:36 2014 UTC. See notes.
PRs for manpage 'syslogd(8)':
S | Submitted | Tracker | Resp. | Description |
---|---|---|---|---|
o | 2012/07/07 | standards/169697 | standards | syslogd(8) is not BOM aware |
o | 2011/07/30 | bin/159305 | [request] make syslogd(8) bind to multiple specific IPs | |
o | 2005/10/30 | bin/88215 | [patch] syslogd(8) does not pass cleanly parameters to cfline() | |
o | 2005/01/27 | bin/76736 | syslogd(8) pipelines losing messages | |
o | 2004/06/25 | bin/68328 | [patch] syslogd(8) enable configuration of extra listen sockets in syslog.conf | |
o | 2002/09/19 | bin/42974 | [patch] syslogd(8): add ISO 8601 date format 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.