On Sun, Jul 09, 2006 at 09:22:05PM +0200, Paul de Weerd wrote:
> Sure, just 'dhclient ${if}'. When 'something' (even another dhclient
> process) touches the networking config of a dhclient-configured
> interface, dhclient will exit (as not to change the new config later).
Not true. I started five instances of ``dhclient trunk0'' on my laptop
two seconds apart, and all five are still running:
Jul 9 14:34:40 whelp dhclient[5289]: DHCPREQUEST on trunk0 to 192.168.0.12
port 67
Jul 9 14:34:40 whelp dhclient[5289]: DHCPACK from 192.168.0.12
Jul 9 14:34:40 whelp dhclient[5289]: bound to 192.168.0.50 -- renewal in 60
seconds.
Jul 9 14:34:42 whelp dhclient[20283]: DHCPREQUEST on trunk0 to 192.168.0.12
port 67
Jul 9 14:34:42 whelp dhclient[20283]: DHCPACK from 192.168.0.12
Jul 9 14:34:42 whelp dhclient[20283]: bound to 192.168.0.50 -- renewal in 60
seconds.
Jul 9 14:34:44 whelp dhclient[31937]: DHCPREQUEST on trunk0 to 192.168.0.12
port 67
Jul 9 14:34:44 whelp dhclient[31937]: DHCPACK from 192.168.0.12
Jul 9 14:34:44 whelp dhclient[31937]: bound to 192.168.0.50 -- renewal in 60
seconds.
Jul 9 14:34:46 whelp dhclient[407]: DHCPREQUEST on trunk0 to 192.168.0.12 port
67
Jul 9 14:34:46 whelp dhclient[407]: DHCPACK from 192.168.0.12
Jul 9 14:34:46 whelp dhclient[407]: bound to 192.168.0.50 -- renewal in 60
seconds.
Jul 9 14:34:48 whelp dhclient[13503]: DHCPREQUEST on trunk0 to 192.168.0.12
port 67
Jul 9 14:34:48 whelp dhclient[13503]: DHCPACK from 192.168.0.12
Jul 9 14:34:48 whelp dhclient[13503]: bound to 192.168.0.50 -- renewal in 60
seconds.
