Sim wrote: > > Without "ntpd -gqx" in "init.d/ntpd" you can show this: ( /var/log/message ) > > Nov 16 14:55:55 ns2 ntpd[15873]: sendto(217.114.97.97): Bad file descriptor > Nov 16 14:55:56 ns2 ntpd[15873]: sendto(217.125.14.244): Bad file descriptor > Nov 16 14:55:57 ns2 ntpd[15873]: sendto(217.114.97.97): Bad file descriptor > Nov 16 14:55:57 ns2 ntpd[15873]: sendto(213.84.230.57): Bad file descriptor > Nov 16 14:55:58 ns2 ntpd[15873]: sendto(217.125.14.244): Bad file descriptor > Nov 16 14:55:59 ns2 ntpd[15873]: sendto(217.114.97.97): Bad file descriptor > Nov 16 14:55:59 ns2 ntpd[15873]: sendto(213.84.230.57): Bad file descriptor > > Is "ntpd -gqx" essential after startup?
It has not been there forever, so it's not critical. However, if the hardware clock is out of sync, the system clock will also be out of sync for quite some time. -gqx essensially sets the system clock hard based on the network time. Does the error messages go away after a manual ntpd -gqx? c -- Christian Haugan Toldnes Trustix Developer _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
