On Saturday 08 September 2007, Andy Green wrote: >Somebody in the thread at some point said: >>>> 128.439 -3332.9 1608.39 [root@frontend_light ~]# ntpstat >>>> unsynchronised >>>> time server re-starting > >Is ntpd running after this? > ># ps -Af | grep ntpd > >>> And why is it restarting? I don't know the answer there, but someplace >>> in a log, there should be a clue. >> >> I don't know either... Above I provided all the logs regarding ntpd. >> There's nothing special, really... It's almost the same as on my >> Fedora Core 6 machine, except that ntp here is not getting synced... > >I guess I would strace ntpd, then. If it was selinux, you'd be seeing >avc messages in your /var/log/messages anyway. I did not see any avc msgs in my logs at the time I installed F7 on my lappy. IIRC I had to strace it myself to see that, but the message I saw in the strace output never made it to the logs. ># service ntpd stop ># strace -f ntpd -u ntp:ntp -p /var/run/ntpd.pid -g > >-Andy -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) interrupt configuration error