On Thursday night, I emerged some packages
Thu Feb 23 23:26:44 2012 >>> net-libs/webkit-gtk-1.6.3-r300
Thu Feb 23 23:29:44 2012 >>> www-client/midori-0.4.3
Thu Feb 23 23:45:36 2012 >>> sys-apps/portage-2.1.10.49
Thu Feb 23 23:52:50 2012 >>> media-libs/libpng-1.5.9
Thu Feb 23 23:53:45 2012 >>> sys-apps/openrc-0.9.9
Thu Feb 23 23:56:43 2012 >>> dev-libs/libgcrypt-1.5.0-r2
Thu Feb 23 23:58:35 2012 >>> media-libs/libmikmod-3.2.0_beta2-r5
Thu Feb 23 23:59:20 2012 >>> media-libs/vo-aacenc-0.1.2
Fri Feb 24 00:00:44 2012 >>> dev-libs/libevent-2.0.17
Fri Feb 24 00:06:11 2012 >>> dev-libs/libxml2-2.7.8-r5
Fri Feb 24 00:07:26 2012 >>> media-sound/alsa-utils-1.0.25-r1
Fri Feb 24 00:08:35 2012 >>> sys-apps/file-5.11
Fri Feb 24 00:10:28 2012 >>> media-libs/imlib2-1.4.5
Fri Feb 24 00:15:00 2012 >>> sys-apps/util-linux-2.20.1-r2
Fri Feb 24 00:15:18 2012 >>> dev-util/intltool-0.50.1
Fri Feb 24 00:19:57 2012 >>> net-print/hplip-3.12.2-r1
Fri Feb 24 00:23:30 2012 >>> media-sound/mpd-0.16.7
Fri Feb 24 00:23:47 2012 >>> dev-tex/latexmk-430a
Fri Feb 24 00:24:20 2012 >>> dev-tex/latex-beamer-3.13
On Friday morning, I started having network problems. wicd would try
to connect to the access point, and fail.
[ 49.754744] r8169 0000:01:00.0: eth0: link down
[ 50.958354] r8169 0000:01:00.0: eth0: link down
[ 52.349167] wlan0: authenticate with 00:01:e3:4b:4a:6d (try 1)
[ 52.355694] wlan0: authenticated
[ 52.355762] wlan0: associate with 00:01:e3:4b:4a:6d (try 1)
[ 52.358116] wlan0: RX AssocResp from 00:01:e3:4b:4a:6d (capab=0x411 status=0
aid=6)
[ 52.358130] wlan0: associated
[ 58.579496] wlan0: deauthenticating from 00:01:e3:4b:4a:6d by local choice
(reason=3)
[ 58.589726] cfg80211: Calling CRDA to update world regulatory domain
[ 58.751572] r8169 0000:01:00.0: eth0: link down
[ 59.954878] r8169 0000:01:00.0: eth0: link down
[ 61.359184] wlan0: authenticate with 00:01:e3:4b:4a:6d (try 1)
[ 61.365490] wlan0: authenticated
[ 61.365561] wlan0: associate with 00:01:e3:4b:4a:6d (try 1)
[ 61.367884] wlan0: RX AssocResp from 00:01:e3:4b:4a:6d (capab=0x411 status=0
aid=6)
[ 61.367898] wlan0: associated
[ 65.108874] wlan0: deauthenticating from 00:01:e3:4b:4a:6d by local choice
(reason=3)
[ 65.119716] cfg80211: Calling CRDA to update world regulatory domain
[ 65.295639] r8169 0000:01:00.0: eth0: link down
[ 262.492240] r8169 0000:01:00.0: eth0: link down
A bit of tracking plus memories of bygone days led me to realise that,
for some reason, the two copies of dhcpcd client were being run! One
was started by wicd, after it associates to the AP. But how'bout the
other one?
Well, on boot up this morning, I saw that, for the first time in a
*very long while* that DHCPCD is being started at boot time as a
service. Now, I am sure I didn't include it as a service.
Gee-Mi-Ni ~ # rc-update show
alsasound | default
bootmisc | boot
consolefont | boot
dbus | default
devfs | sysinit
dmesg | sysinit
fsck | boot
gpm | default
hostname | boot
hwclock | boot
keymaps | boot
killprocs | shutdown
local | default nonetwork
localmount | boot
metalog | boot
modules | boot
mount-ro | shutdown
mtab | boot
net.lo | boot
netmount | default
procfs | boot
root | boot
savecache | shutdown
swap | boot
swapfiles | boot
sysctl | boot
termencoding | boot
udev | sysinit
udev-postmount | default
urandom | boot
wicd | boot
Okay, on the other hand rc-status showed something I haven't seen before
Dynamic Runlevel: needed
sysfs [started]
dhcpcd [started]
Huh, simple enough, some other service needs dhcpcd to be running. Okay. Let me
see which one it is:
Gee-Mi-Ni init.d # grep dhcpcd /etc/init.d/*
/etc/init.d/dhcpcd:command=/sbin/dhcpcd
/etc/init.d/dhcpcd:pidfile=/var/run/dhcpcd.pid
/etc/init.d/wpa_supplicant: before dns dhcpcd net
uh, apparently none of them?
Can someone help me figure out how to find the offending initscript that is
needlessly calling dhcpcd?
Cheers,
W
--
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire
et vice versa ~~~ I. Newton
