How did it end up looking?
Just a reminder really, since I use this already/anyway. :)
2012/7/27 Kenneth R Westerback kwesterb...@rogers.com:
I like this on first read. In fact I thought this already existed.
I'll actually look more closely at the code tomorrow.
Ken
On Thu, Jul 26,
On Fri, Jul 27, 2012 at 00:42, Brynet wrote:
On Thu, Jul 26, 2012 at 10:09:28PM -0400, Ted Unangst wrote:
I have a system with two network interfaces (em0 and em1), running dhcp
on both. Both dhcp servers provide me with a nameserver, but only one
of them works (I can't fix this). There is a
One can set a dhclient-script to ignore things and then call
the real dhclient-script, but I like this diff better.
Penned by Kenneth R Westerback on 20120726 21:43.39, we have:
| I like this on first read. In fact I thought this already existed.
| I'll actually look more closely at the code
Ted Unangst wrote:
[...] I just want to say pretend this option did not arrive.
Diff below adds a little support for an ignore keyword. Like
supersede, except don't actually use the supplied value.
Put another way, dhclient has a default permit policy (it will use
any nameserver information
I have a system with two network interfaces (em0 and em1), running dhcp
on both. Both dhcp servers provide me with a nameserver, but only one
of them works (I can't fix this). There is a config file for dhclient
I can use, but it only supports the supersede keyword. I don't want
to statically
I like this on first read. In fact I thought this already existed.
I'll actually look more closely at the code tomorrow.
Ken
On Thu, Jul 26, 2012 at 10:09:28PM -0400, Ted Unangst wrote:
I have a system with two network interfaces (em0 and em1), running dhcp
on both. Both dhcp servers
On Thu, Jul 26, 2012 at 10:09:28PM -0400, Ted Unangst wrote:
I have a system with two network interfaces (em0 and em1), running dhcp
on both. Both dhcp servers provide me with a nameserver, but only one
of them works (I can't fix this). There is a config file for dhclient
I can use, but it
