As in the title - if the ntpd daemon is launched with -s, then nothing will be written to the log until it exits, where it writes the normal termination message. No errors are produced, and the daemon does operate correctly (verified via strace). Reproducible: Always Steps to Reproduce: 1. Execute ntpd -s 2. Note that no information is written to /var/log/messages while ntpd is running 3. Now compare to launching ntpd with no options Actual Results: With ntpd -s, the software should still write to log, the -s flag claims to only "Set the time immediately at startup if the local clock is off by more than 180 seconds" Expected Results: The log should have messages from ntpd like below: Mar 1 19:34:44 gentoo ntpd[330]: ntp engine ready Mar 1 19:35:01 gentoo ntpd[330]: peer 146.83.183.179 now valid Mar 1 19:35:02 gentoo ntpd[330]: peer 193.201.200.74 now valid Mar 1 19:35:03 gentoo ntpd[330]: peer 91.121.3.188 now valid Mar 1 19:35:06 gentoo ntpd[330]: peer 89.108.81.77 now valid Mar 1 19:35:06 gentoo ntpd[330]: peer 85.130.111.169 now valid Mar 1 19:35:08 gentoo ntpd[330]: peer 130.226.232.145 now valid Mar 1 19:35:09 gentoo ntpd[330]: peer 82.96.64.2 now valid Mar 1 19:35:09 gentoo ntpd[330]: peer 84.2.40.31 now valid etc
the initial lack of logging is by design. it's supposed to start up in the fg, set the time, and then daemonize and start logging. i guess the logic gets mixed up at the end somewhere.
`ntpd -s' should not be used normally, this really should be reported upstream.
