PRs for manpage 'ntpd(8)'
This is an experimental report containing PRs for manpage 'ntpd(8)' as of Fri May 30 07:38:28 2014 UTC. See notes.
PRs for manpage 'ntpd(8)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2013/12/31 | bin/185371 | ntpd(8) vulnerable to being used for DDOS | |
| o | 2013/11/14 | bin/183967 | ntpd(8): ntpd logs different version to syslog versus --version | |
| o | 2013/06/25 | bin/179963 | ntpd(8) tries to bind IFDISABLED IPv6 addresses | |
| o | 2012/06/26 | bin/169439 | [patch] ntpd(8): Stock ntpd segfaults when used with GPS pps source | |
| o | 2011/05/17 | bin/157104 | [patch] ntpd(8) with -DDISABLE_IPV6 gives a lot of error messages | |
| o | 2011/04/18 | bin/156484 | ntpd(8) regularly flips between PLL and FLL mode (time sync status change 6001/2001) | |
| o | 2010/11/23 | bin/152525 | ntpd(8) on 8.1 loops on select() with EBADF | |
| o | 2010/07/22 | bin/148836 | roberto | ntpd(8): [patch] Update to NTP in base system |
| o | 2010/03/16 | conf/144804 | ntpd(8) cannot resolve hostnames at system start | |
| o | 2009/12/08 | bin/141264 | ntpd(8) crashes when tries to use an oncore reference clock | |
| o | 2008/11/15 | bin/128886 | ntpd(8): ntpd -L flag doesn't work | |
| o | 2008/05/27 | bin/124049 | ntpd(8): ntpd is crashing at startup | |
| o | 2008/02/24 | bin/121059 | ntpd(8) doesn't sync with servers after dhclient changes IP | |
| o | 2007/07/30 | bin/115054 | ntpd(8): NTP errors out on startup but restart of NTP fixes problem | |
| o | 2007/06/11 | conf/113552 | [request] ntpd(8) driftfile default location inconsistently referenced |
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.