Emmanuel Dreyfus wrote: > Oliver Fromme wrote: > > ntpdate is bad and should never be used. I think it has > > even been officially deprecated and will be removed in the > > future (at least the manpage says so). > > ntpdate is perfect for the initial sync before ntpd or any daemon > has started. I'm sorry I have to disagree. ntpdate is evil and has to die. :-) Seriously, ntpd should be run with the -g option. It does the same as running ntpdate once (i.e. performing one initial step if necessary), but with much better accuracy. It completely replaces ntpdate. > I beleive it's even made for that purpose: ntpd will > refuse to work if the clock skew is too large at startup. Use ntpd -g. ntpdate is a left-over from ancient versions of the xntpd software suite, and it only exists for historical reasons. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Gesch\ufffdftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M\ufffdn- chen, HRB 125758, Gesch\ufffdftsf\ufffdhrer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "[...] one observation we can make here is that Python makes an excellent pseudocoding language, with the wonderful attribute that it can actually be executed." -- Bruce Eckel
Message
Re: [milter-greylist] mxsync not quite working properly
2007-04-27 by Oliver Fromme
Attachments
- No local attachments were found for this message.