Re: [PATCH 0/2] ntpd: retry name-resolution until success

2016-02-14 Thread Laurent Bercot
On 11/02/2016 13:34, Bastian Bittorf wrote: with OpenWrt there is a feature where you have a "protected" area in RAM which is not lost during reboot and used for having a crashlog safed over a reboot. ("crashlog.o") see e.g: https://dev.openwrt.org/browser/trunk/target/linux/generic/patches-4.4/

Re: [PATCH 0/2] ntpd: retry name-resolution until success

2016-02-11 Thread Bastian Bittorf
* Laurent Bercot [11.02.2016 13:27]: > I wonder if there are better solutions. just for completeness: with OpenWrt there is a feature where you have a "protected" area in RAM which is not lost during reboot and used for having a crashlog safed over a reboot. ("crashlog.o") see e.g: https://dev

Re: [PATCH 0/2] ntpd: retry name-resolution until success

2016-02-11 Thread Laurent Bercot
On 11/02/2016 12:44, Denys Vlasenko wrote: In practice it is impossible to make daemons 100% robust. Because of this, we have several generations of babysitting tools which restart daemons on exit. I don't think it's the correct argument. Supervision tools should not be an excuse to be complac

Re: [PATCH 0/2] ntpd: retry name-resolution until success

2016-02-11 Thread Denys Vlasenko
On Thu, Feb 11, 2016 at 6:05 AM, Rich Felker wrote: > On Thu, Feb 11, 2016 at 05:56:06AM +0100, Denys Vlasenko wrote: >> On Thu, Feb 4, 2016 at 2:43 PM, Mark O'Donovan wrote: >> > This is an attempt to fix bug 8131: >> > ntpd: should retry on name resolving error >> >> Should it? >> Why doesn't

Re: [PATCH 0/2] ntpd: retry name-resolution until success

2016-02-10 Thread Rich Felker
On Thu, Feb 11, 2016 at 05:56:06AM +0100, Denys Vlasenko wrote: > On Thu, Feb 4, 2016 at 2:43 PM, Mark O'Donovan wrote: > > This is an attempt to fix bug 8131: > > ntpd: should retry on name resolving error > > Should it? > Why doesn't ping do this? telnet? netcat? No network utility does this.

Re: [PATCH 0/2] ntpd: retry name-resolution until success

2016-02-10 Thread Denys Vlasenko
On Thu, Feb 4, 2016 at 2:43 PM, Mark O'Donovan wrote: > This is an attempt to fix bug 8131: > ntpd: should retry on name resolving error Should it? Why doesn't ping do this? telnet? netcat? No network utility does this. Adding it to ntpd only would be inconsistent. I can see why this request c

[PATCH 0/2] ntpd: retry name-resolution until success

2016-02-04 Thread Mark O'Donovan
This is an attempt to fix bug 8131: ntpd: should retry on name resolving error ntpd init now waits for hostname-resolution to succeed instead of quitting. If there is no network/dns available then the command will not daemonise so the second patch moves the daemonise code before the peer-adding