| Re: [chrony-dev] New online/offline command |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
On Wed, May 23, 2018 at 04:44:30PM +0200, Christian Ehrhardt wrote:
> No I'm fine with a single command.
> If it is low on cpu consumption and fast.
> We have to consider that in some environments you might have plenty
> (really a lot) of changes ongoing.
> And you might get a notification for each of them.
How much is plenty? I guess we could use a delay and batch all
requests in some interval (e.g. one second), but I think I'd prefer if
it was executed synchronously. It's simpler and there will be no
surprises if someone runs the new command and then follows it with the
old online command, which might have no effect.
> With just one command neither Stephens nor my suggestion make sense.
> How about just "probe" then?
I'm not sure. What exactly are we probing here? There are no packets
exchanged. It's just a local check of the routing configuration.
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.