dhcpcd -k ${1}
is more graceful anyway. Try that in your /etc/rc.d/network replacing that kill line.
]]># find / -iname '*.pid'
/var/run/klogd.pid
/var/run/syslogd.pid
/var/run/crond.pid
/var/run/portmap.pid
/var/run/inetd.pid
/var/run/cardmgr.pid
/var/run/xdm.pid
#
# cat /etc/dhcpc/dhcpcd-eth0.info
IPADDR=192.168.2.16
NETMASK=255.255.255.0
NETWORK=192.168.2.0
BROADCAST=255.255.255.255
GATEWAY=192.168.2.1
DOMAIN='REDLAN'
DNS=192.168.2.1
DHCPSID=192.168.2.1
DHCPGIADDR=0.0.0.0
DHCPSIADDR=0.0.0.0
DHCPCHADDR=08:00:46:0A:F6:6D
DHCPSHADDR=00:04:E2:3D:11:B2
DHCPSNAME='ÿ'
LEASETIME=4294967295
RENEWALTIME=2147483647
REBINDTIME=3758096383
INTERFACE='eth0'
CLASSID='Linux 2.4.22-ck2 i686'
CLIENTID=08:00:46:0A:F6:6D
#
So, .... Is there a better way to write the network script to account for this and short-lease times, both? If so, I would be glad to submit a bug-report for future versions.
Thanx, again for your insights.
]]>/bin/kill `cat /etc/dhcpc/dhcpcd-${1}.pid`
to
dhcpcd -k
i had some months ago the same problem ... but it is not (directly) a arch-related problem:
if you have your laptop connected to a LAN that has a dhcp-server that gives you back "infinite release time" (this means the IP you get is valid for infinite time), then dhcpcd will shut down after setting IP correctly ... this leads while shutdowning that if you stop the network you have the problem with shuting down dhcpcd --- because it is shutted down at startup (just after configuring your IP and gateway)
also some DSL-routers have in their dhcps "infinite release time" as default or not changable :-(
this error is not that important ... if you worry getting [failed], then edit the rc.d/network script (remove this line) --- this is not really functional, but easy done and then you do not longer get [failed] :-)
]]>$ ls -lha /etc/dhcpc/
total 16K
drwxr-xr-x 2 root root 160 Oct 21 21:13 .
drwxr-xr-x 30 root root 2.7K Oct 21 21:13 ..
-rw------- 1 root root 136 Oct 21 21:13 dhcpcd-eth0.cache
-rw-r--r-- 1 root root 412 Oct 21 21:13 dhcpcd-eth0.info
-rw-r--r-- 1 root root 412 Oct 21 21:13 dhcpcd-eth0.info.old
$ ls -lha /var/run/
total 43K
drwxr-xr-x 6 root root 416 Oct 21 20:39 .
drwxr-xr-x 14 root root 360 Oct 17 13:11 ..
-rw-r--r-- 1 root root 4 Oct 21 20:39 cardmgr.pid
-rw-r--r-- 1 root root 1 Oct 21 20:39 crond.pid
drwxr-xr-x 2 root root 144 Oct 21 21:13 daemons
-rw-r--r-- 1 root root 4 Oct 21 20:39 inetd.pid
-rw-r--r-- 1 root root 3 Oct 21 20:38 klogd.pid
-rw-r--r-- 1 root root 1 Oct 21 20:39 portmap.pid
-rw-r--r-- 1 root root 512 Oct 21 20:38 random-seed
-rw-r--r-- 1 root root 3 Oct 21 20:38 syslogd.pid
drwx------ 2 root root 48 Oct 8 22:09 usb
-rw-r--r-- 1 root root 4.9K Oct 21 20:40 utmp
drwxr-xr-x 2 root root 80 Oct 21 20:39 xauth
-rw-r--r-- 1 root root 4 Oct 21 20:39 xdm.pid
drwxr-xr-x 2 root root 104 Oct 21 20:39 xdmctl
I've been using dhcp ever since 0.4(dragon) and it has always done this(!).
]]>Here is the actual output:
# /etc/rc.d/network stop
| Stopping Network [busy] cat: /etc/dhcpc/dhcpcd-eth0.pid: No such file or directory
Usage:
kill pid ... Send SIGTERM to every process listed.
kill signal pid ... Send a signal to every process listed.
kill -s signal pid ... Send a signal to every process listed.
kill -l List all signal names.
kill -L List all signal names in a nice table.
kill -l signal Convert between signal numbers and names.
[fail]
Thanx.
]]>