My boot process pauses for about two minutes. See the last two lines of: Nov 13 19:03:51 localhost chronyd[3545]: chronyd version 1.21 starting Nov 13 19:03:57 localhost chronyd[3545]: Initial txc.tick=10000 txc.freq=0 (0.00000000) txc.offset=0 => hz=100 shift_hz=7 Nov 13 19:03:57 localhost chronyd[3545]: set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000 Nov 13 19:03:58 localhost chronyd[3545]: Linux kernel major=2 minor=6 patch=18 Nov 13 19:03:58 localhost chronyd[3545]: calculated_freq_scale=0.99902439 freq_scale=0.99902439 Nov 13 19:05:52 localhost chronyd[3545]: Bad command logon from 127.0.0.1 port 32771 (md5_ok=1 valid_ts=0)
The route command is very quick: # time route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 default router 0.0.0.0 UG 0 0 0 eth0 real 0m0.002s user 0m0.000s sys 0m0.000s so this is not the culprit. Any other ideas? In fact, if I cut and paste the following lines into my shell: /etc/init.d/chrony stop PATH=/bin:/usr/bin:/sbin:/usr/sbin DAEMON=/usr/sbin/chronyd FLAGS="defaults" NAME="chronyd" DESC="time daemon" start-stop-daemon --start --verbose --exec $DAEMON sleep 1 route 2>/dev/null | grep -q default && /etc/ppp/ip-up.d/chrony > /dev/null || true they run quickly. But if I do /etc/init.d/chrony stop /etc/init.d/chrony start the start command takes a couple of minutes. With some echo statements, I've now narrowed it down to the /etc/ppp/ip-up.d/chrony script. A ps shows that chronyc is running during the delay. So the logon error message is probably related. I put the following lines: password fKWJxHwd online burst 5/10 quit in /tmp/ch, and "cat /tmp/ch | chronyc" runs quickly and without errors. So I can't figure out why things are slow when run through the /etc/init.d/chrony script. I tried changing the shell there to bash, but that didn't help either. Any ideas? Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
