On Thu, Aug 23, 2012 at 03:35:56PM +0100, Tomalak Geret'kal wrote:
> Hey
>
> My /etc/chrony.conf is owned by an automated tool (of sorts) which
> currently has to kill the chrony process and restart it, in order
> for chrony to pick up new config when it's made. This doesn't feel
> too robust, sin
On 03/09/2012 15:35, Miroslav Lichvar wrote:
On Thu, Aug 23, 2012 at 03:35:56PM +0100, Tomalak Geret'kal wrote:
Hey
My /etc/chrony.conf is owned by an automated tool (of sorts) which
currently has to kill the chrony process and restart it, in order
for chrony to pick up new config when it's mad
Hey
My /etc/chrony.conf is owned by an automated tool (of sorts)
which currently has to kill the chrony process and restart
it, in order for chrony to pick up new config when it's
made. This doesn't feel too robust, since the kill could
theoretically fail and then the restart wouldn't work
e
