On Mon, Jul 18, 2011 at 6:31 PM, Theo de Raadt <dera...@cvs.openbsd.org> wrote: > There is ntp everywhere. Use: > > server myownmachine.mynetwork.xx > servers pool.ntp.org
I often plug this laptop in to unknown stuff (or mirror/span ports or ethernet taps) and run tcpdump so I don't want to run any daemons that generate traffic. It's a little netbook and I use it for network troubleshooting only - it isn't a normal laptop setup. My main laptop does run ntpd all the time though. I guess I will just use ntpd from now on and manually stop it if needed. Of course, with ntpd_flags="-s" in my rc.conf.local I won't be able to start it again without jumping the clock. What do you think of making -s the default in /etc/rc.d/ntpd so it always syncs during boot but not any subsequent manual starts/restarts? Then one would just use ntpd_flags="" in rc.conf.local (or "-S" to disable the auto sync if desired). If ntpd crashed on a server the only way to safely start it again would be to reboot (or run ntpd directly but that negates the whole point of rc.d). >> Running ntpd isn't >> useful then and I would have to kill it after it set the time. I >> could run rdate manually after boot but the clock jumps. > > That is why you should not run rdate. ntpd -s does exactly the same thing. Clock jumps are fine during boot. > The diff you supplied is exactly what I deleted previously. No. Since rdate_flags was left in rc.conf, I thought the removal may have been an oversight. Daniel
