Poštni seznam arhiviranih sporo?il | Nazaj na seznam |
|
---|
On 10/07/06 03:43 pm, Carl Gehr thus wrote :I generally run dhcpmon -t. One possibility, I found I had to add -d to dhcpstrt such as dhcpstrt -d 5 lan0. When I was booting up without it xwlan did not get an ip address because it could not down the dhcp client until it had timed out in the foreground. Running dhcpmon -t to down it would not really work until it had timed out.
Lewis,Oops. Yes, now how did I miss that when I read your post the first time? Too much on my mind...
I went through exactly the steps, in the sequence shown below.
#2 Killed it.
#3 Reran the script which restarted DHCPCD
And, as you can see, #4 Closed DHCPMon and Restarted it.
Just for the exercise, I reran the script again just now. The PID forAll I can tell you Carl is that I get the same issue here, so I just run the script a couple more times until DHCPMON picks up on it. I don't close DHCPMON, either; I just rerun the script, and eventually, DHCPMON allows me to select the alternate interface.
the DHCPCD changed from 109 as it was after the previous exercise and
it is now showing as 216.
If there's something else to look at [and you can tell me how], I'll be
happy to try.
I think I mentioned this originally, but if I just bring the system up
with a cable attached at boot-time, DHCPMon displays what it should. The script changes what is displayed to that shown below.
<snip>
Naro?iti: Poro?ilo (Feed),
Izvle?ek (Digest),
Indeks. Odjava E-pošta za mojstra za sezname |