On 17/06/13 05:40, Mario Frasca wrote: > the main problem with this bug is that you can't start 'ntpd' if the > time is not set approximatively correct from the start. take for > example a computer without memory of the outside time (for example > because its battery is faulty), then you somehow need bootstrap the > procedure and chances are that you do not want to do this by hand. > > if you install 'ntpdate' and run it before 'ntpd' starts, things > should go fine.
Hi Mario! Up to a certain extent, starting openntpd with the "-s" parameter set at the /etc/default/openntpd should be coping this, if using any 20080406p version (older version have a bug that makes syslog not to log any time adjustment at all). Greetings, Dererk -- BOFH excuse #180: ether leak -- BOFH excuse #180: ether leak
signature.asc
Description: OpenPGP digital signature