ons, 15 02 2006 kl. 20:39 +0000, skrev Ola Thoresen: > 2006-02-15 Truls Gulbrandsen <trulsg@xxxxxxxxxxxx> wrote > > > > Hi, > > I was wondering if there is a wrong sequence regarding ntpd when booting. > > > > I have noticed that first ntpd tries to sync with server (fails) and > > thereafter starts the ntpd service (success). > > > When starting up, ntpd uses 'ntpdate' with the content of > /etc/ntp/step-tickers as parameter(s) > The default here is a few pool*.ntp.org lines, and I have several times > noticed that this makes the syncing extremely slow - and sometimes > failing. > If I sync with just one or two local ntp-servers the startup is a _lot_ > faster. > > ntpd however runs as a daemon, and will start even without being able to > connect to any servers, as it will just try to resync the clock as soon > as one or more servers are available. > > So try to change your step-tickers so it just contains IE. ntp.uio.no > (as you are here in Norwaym that one is quite reliable - your ISP might > have another timeserver available, just add that one as well to get som > redundancy). Hopefully this will help. Still it fails for network manager set ups as that service starts after the ntp service - thus causing it to fail on every boot. - David -- Obligatory shameless blog plug - the GNOME commentary located at: www.lovesunix.net/blog -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list