Hello,
is there still any concern regarding this patch ? Is it possible to
integrate it ?
For in formation, it has been integrated in the busybox version we use
at Parrot and is used with no known problem so far.
Thank you.
2016-02-04 12:42 GMT+01:00 Nicolas CARRIER :
> Please find attached the
On Thu, Feb 11, 2016 at 05:59:39AM +0100, Denys Vlasenko wrote:
> On Tue, Feb 9, 2016 at 6:23 PM, Balaji Punnuru
> wrote:
> > When a dhcp server responds with a domain name that ends with a ".",
> > domain name validation is failing which leads to populating domain bad in
> > resolv.conf
> >
> >
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.
On Tue, Feb 9, 2016 at 6:23 PM, Balaji Punnuru wrote:
> When a dhcp server responds with a domain name that ends with a ".",
> domain name validation is failing which leads to populating domain bad in
> resolv.conf
>
> Domain name ending with . is a valid syntax according RFC-1034.
>
> The Patch f
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
On Thu, Feb 4, 2016 at 1:43 PM, Mark O'Donovan wrote:
> Command otherwise may hang indefinately if unable to resolve peers.
> ---
> networking/ntpd.c | 9 +
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/networking/ntpd.c b/networking/ntpd.c
> index 3273cdd..25e19f8 10
