It seems clear to me that once again, we have learned that in general we
cannot expect ntpd to "restart from scratch" without stopping and
restarting the process.
Again, items which make this infeasible include:
- chroot
- drop privs
As the above features are probably the most important to the s
Harlan Stenn wrote:
> Rob writes:
>> Harlan Stenn wrote:
>> > Amongst the many reasons why we did not let SIGHUP restart the daemon
>> > was that back in the old days we used modem drivers a lot more often.
>> > The HUP signal was generic - it was not really associated with any
>> > specific devi
On Thu, Apr 10, 2014 at 08:20:59PM +, Harlan Stenn wrote:
> Rob writes:
> > Furthermore, the "simple solution" of having SIGHUP perform an exec
> > of the same binary, thus in fact restarting the entire process and
> > losing all state information, is not the only possible solution.
>
> If the
