On Tue, 02 Sep 2008 13:34:18 -0500 John Hasler wrote: > Francesco Poli writes: > > ...I've just tried to discard the rtcdevice directive... > > "rtcdevice" merely tells chronyd that the rtc is in a nonstandard place.
Yes, I am aware of that. It's precisely why I inserted that directive into /etc/chrony/chrony.conf: I currently have no /dev/rtc, but /dev/rtc0 instead. And this will hold until I upgrade udev. > In its absence /dev/rtc is assumed. Yes, that's why chronyd logs error messages in its absence: my system currently lacks /dev/rtc. > To stop chronyd from messing with the > rtc comment out the "rtcfile" directive (I agree that this is confusing). But this would entirely disable the use of RTC, wouldn't it? > > > When I first rebooted the box with Linux kernel 2.6.26, the above error > > messages were logged, but then chronyd did nothing else for about 95 s > > ... Maybe I was just too impatient? > > The "netstat" call in the initscript can hang longer than that (yes, this > is a bug). Ah, I had never noticed before... -- http://frx.netsons.org/doc/index.html#nanodocs The nano-document series is here! ..................................................... Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
pgp3XHKFeAcVv.pgp
Description: PGP signature
