On Mon, Aug 02, 2010 at 04:24:52PM -0500, John Hasler wrote: > Would it be unacceptable for Chrony to step the clock (particularly > back) during boot? This would only happen when the clock was at least > 30 seconds off but I'm concerned that it might screw some of the daemons > that might already have started. If Chrony can't step the clock it > would have to slew it (which can take hours for large errors) or give > up. This would only happen on rare occasions. dovecot kills itself when time moves backwards too much. See <http://wiki.dovecot.org/TimeMovedBackwards>. I don't think it would be okay unless you can either make sure that dovecot handles this gracefully (and that involves not needing to be restarted or disconnecting users) or change the time only before normal (non-time-related) services start. I think the latter is prudent anyway. Other than this, I don't know any reason why you shouldn't. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Attachment:
signature.asc
Description: Digital signature