Why can't ExecStopPre= be used to abort stopping a (broken) service?

Miroslav Lichvar mlichvar at redhat.com
Wed Jul 17 15:50:15 UTC 2013


On Wed, Jul 17, 2013 at 03:47:27PM +0200, Lennart Poettering wrote:
> On Wed, 17.07.13 11:29, Miroslav Lichvar (mlichvar at redhat.com) wrote:
> > An even better example might be the -R option, which tells chronyd to
> > not step the clock on start. If it was used on service restart, we
> > would be sure there are no time jumps when the chrony package is
> > upgraded.
> 
> But for -R even more looking at the clock is actually the better choice
> and already what happens, no? I mean, the stepping is only done if the
> time difference is greater than some threshold. That sounds like a much
> better solution, since it always works.

The clock could be so bad (think virtual machines) that it can't be
constantly kept below the threshold. Unlikely, but certainly possible.
The -R option would guarantee there are no steps after the first
start.

-- 
Miroslav Lichvar


More information about the devel mailing list