Re: dhclient implementation

2011-08-27 Thread Iñigo Ortiz de Urbina
On Sat, Aug 27, 2011 at 1:01 AM, Jona Joachim j...@hcl-club.lu wrote: On 2011-08-26, I??igo Ortiz de Urbina inigoortizdeurb...@gmail.com wrote: Supersede gives me what I want. It just felt weird those entries ended up on resolv.conf when I had not requested them. Thanks and sorry for the

Re: dhclient implementation

2011-08-27 Thread Jona Joachim
On 2011-08-27, I??igo Ortiz de Urbina inigoortizdeurb...@gmail.com wrote: On Sat, Aug 27, 2011 at 1:01 AM, Jona Joachim j...@hcl-club.lu wrote: On 2011-08-26, I??igo Ortiz de Urbina inigoortizdeurb...@gmail.com wrote: Supersede gives me what I want. It just felt weird those entries ended up on

dhclient implementation

2011-08-26 Thread Iñigo Ortiz de Urbina
Hi all users and developers I simply noticed what I would call a weird behaviour on my 32 bit 4.9 GENERIC#671 box's dhclient, which I hope is not the expected behavior. While reading RFC2131, I didnt find any sentence stating or implying that is the desired behavior, as in a server MUST Say

Re: dhclient implementation

2011-08-26 Thread Jona Joachim
On 2011-08-26, I?igo Ortiz de Urbina tarom...@gmail.com wrote: Hi all users and developers I simply noticed what I would call a weird behaviour on my 32 bit 4.9 GENERIC#671 box's dhclient, which I hope is not the expected behavior. While reading RFC2131, I didnt find any sentence stating or

Re: dhclient implementation

2011-08-26 Thread Iñigo Ortiz de Urbina
Supersede gives me what I want. It just felt weird those entries ended up on resolv.conf when I had not requested them. Thanks and sorry for the noise. 2011/8/27 IC1igo Ortiz de Urbina tarom...@gmail.com: Hi all users and developers I simply noticed what I would call a weird behaviour on my

Re: dhclient implementation

2011-08-26 Thread Jona Joachim
On 2011-08-26, I??igo Ortiz de Urbina inigoortizdeurb...@gmail.com wrote: Supersede gives me what I want. It just felt weird those entries ended up on resolv.conf when I had not requested them. Thanks and sorry for the noise. This is expected behaviour for the prepend option, it does just