On Sat, 18 Jan 2014 00:24, Linda Walsh
Carlos E. R. wrote:
On 2014-01-17 20:59, Achim Gratz wrote:
I want it to start as fast as it did before, taking a few seconds at maximum. From playing around with starting and stopping it manually the problem seems to be that during start it seems to traverse a lot of directories and I still haven't got an idea why it does that or how to debug it.
But once systemd tells ntpd to start, if it takes long it does not have to do with systemd at all.
Typical delay cause would be no network, or configured peers not responding fast.
Dunno if it would help in the OP's case, but I keep an old 900MHz Celeron running linux almost exclusively to keep track of time when my mainserver goes down.
It used to do dns resolves, but some suse change killed that off, and I haven't bothered to fix it...(sigh)..
Similar setup here. Mini-box with ntp / dnsmasq / snmp dnsmasq was the solution for my dns needs, small, fast, near stable config (just added features) since more than 5 years. Back to OP.: With a harshly limiting config you can drop chroot in most cases. My hint to solving some of your troubles would be: - Do a timing for all your upwards-peers. - Exchange some upwards-peers if needed. Use: http://support.ntp.org/bin/view/Servers/WebHome as a starting point to locate valid timeservers, then take a look at them with "traceroute" to get the ones with the least number of network-hops. For normal servers and desktops, stratum 3 / pool is good enough. Be aware that some 'local' reference clocks (gps-receivers, terristic-broadcast-clocks, etc) can take some time to get started and give valid data. - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org