> The problem is the hard syncing of the time using ntpd -gqx. It does not > time out when using those options. For a system that boots often, and > often has these network problems during boot, that line can be commented > out, and one can do ntpd -gqx manually when the network is up.
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? _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
