Bug 84619

Summary:	net.eth1 doesn't stop dhcpcd correctly
Product:	Gentoo Linux	Reporter:	Martin Gollowitzer <martin.gollowitzer>
Component:	[OLD] baselayout	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED DUPLICATE
Severity:	minor
Priority:	High
Version:	2004.3
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Martin Gollowitzer 2005-03-09 04:50:38 UTC

I've seen a similiar bug (#1260), but this was related to another version of Gentoo. I'm using a 2004.3 stage1 installation. I've got the ipw2100 driver in use for my WLAN card and at the beginning I didn't have problems with the autmatic setup of the card at boot time. I'm not sure when the problem started, but I think it started with the last emerge -uD world. Since then, the dhcpcd isn't killed at shutdown, or at least, the pid-file isn't removed. When I do a /etc/init.d/net.eth1 restart while the system is running, the pid-file will be deleted, but the dhcpcd process is still running (according to ps aux).
Sorry for my English.

Reproducible: Always
Steps to Reproduce:
1.Init 0 + reboot or init 6
2.look at output: staring dhcpcd for eth1 -> dhcpcd already running

Actual Results:  
No IP address assigned to eth1

Expected Results:  
Received IP address 192.168.0.4

Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.4.3-20050110,
glibc-2.3.4.20050125-r0, 2.6.10-gentoo-r7 i686)
=================================================================
System uname: 2.6.10-gentoo-r7 i686 Intel(R) Pentium(R) M processor 1600MHz
Gentoo Base System version 1.6.9
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, Feb 22 2005, 20:57:05)]
dev-lang/python:     2.3.5
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.8.5-r3, 1.5, 1.6.3, 1.9.5, 1.7.9-r1, 1.4_p6
sys-devel/binutils:  2.15.92.0.2-r4
sys-devel/libtool:   1.5.10-r5
virtual/os-headers:  2.4.22-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium3 -pipe -O2 -fomit-frame-pointer -fforce-addr
-frename-registers -fprefetch-loop-arrays -falign-functions=64"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium3 -pipe -O2 -fomit-frame-pointer -fforce-addr
-frename-registers -fprefetch-loop-arrays -falign-functions=64"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://gd.tuwien.ac.at/opsys/linux/gentoo/
ftp://gd.tuwien.ac.at/opsys/linux/gentoo/ http://gentoo.inode.at/
ftp://gentoo.inode.at/source/ http://gd.tuwien.ac.at/opsys/linux/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="x86 X aac aalib acpi alsa arts audiofile avi bash-completion berkdb bidi
bitmap-fonts bzlib cdr crypt cups curl directfb divx4linux dvd emacs emboss
encode esd ethereal exif fam fbcon flac font-server foomaticdb fortran ftp gdbm
gif gpm gtk2 guile icq imagemagick imap imlib java jpeg kde libg++ libwww mad
mikmod mime motif mozilla mp3 mpeg ncurses nls oggvorbis opengl pam pcmcia pda
pdf pdflib perl php png python qt quicktime readline samba sdl spell ssl svga
tcpd tetex tidy tiff truetype truetype-fonts type1-fonts unicode usb xine xml2
xmms xv zlib linguas_de linguas_en"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY

Comment 1 SpanKY gentoo-dev

2005-03-09 17:21:57 UTC

do you use hotplug/coldplug ?

Comment 2 Martin Gollowitzer 2005-03-10 07:25:57 UTC

Yes, I'm using hotplug to load the firmware of the WLAN card.
Sorry for my n00b style of reporting a bug.

Comment 3 Roy Marples (RETIRED) gentoo-dev

2005-03-10 09:15:20 UTC

Could you check that it's not caused by bug #78495?

I suspect this is a dupe

Comment 4 Martin Gollowitzer 2005-03-10 10:23:45 UTC

You were right, it works now. I just wonder why it worked before I updated the system. I try to find out. Thanks guys!

*** This bug has been marked as a duplicate of 78495 ***