dhcpcd works but starts two processes

My setup is working so I really shouldn't try to fix something that
isn't broken but it's bugging me.

On bootup, the /etc/rc.d/rc.inet1 is called only once.
Inside this script, I have put

ps axu | grep dhcpcd | grep -v grep
echo "Starting DHCP for eth0"
/sbin/dhcpcd eth0
echo "Starting DHCP for eth1"
/sbin/dhcpcd eth1
ps axu | grep dhcpcd | grep -v grep

this shows that there are no dhcpcd processes at the start and four
dhcpcd processes after.

the second ps shows

171 /sbin/dhcpcd eth0
174 /sbin/dhcpcd eth0
177 /sbin/dhcpcd eth1
182 /sbin/dhcpcd eth1

You can see that the script isn't being duplicated somewhere or the pid
order would show eth0, eth1, eth0, eth1.

/etc/dhcpc/dhcpcd-eth0.pid contains 174
/etc/dhcpc/dhcpcd-eth1.pid contains 182

It doesn't matter if I kill 171 or 174, eth0 will still lose its
address. (The same goes for eth1)

HOWEVER...

killall dhcpcd
/sbin/dhcpcd eth0
/sbin/dhcpcd eth1

gives both interfaces their addresses back but only results in one
process for each.

Hmmm
Any ideas?

Andy Richardson wrote:
> My setup is working so I really shouldn't try to fix something that
> isn't broken but it's bugging me.
>
> On bootup, the /etc/rc.d/rc.inet1 is called only once.
> [snip]
> Hmmm
> Any ideas?

If you run Slackware, which version ? Normally, rc.inet1 will start
dhcpcd if you don't assign any static ip (in rc.inet1 or rc.inet1.conf
depending on Slackware version). Why did you insert the extra stuff in
rc.inet1 ?

Trygve Selmer wrote:
> If you run Slackware, which version ? Normally, rc.inet1 will start
> dhcpcd if you don't assign any static ip (in rc.inet1 or rc.inet1.conf
> depending on Slackware version). Why did you insert the extra stuff in
> rc.inet1 ?

The extra stuff was just to prove to myself by watching the screen
during boot up that there were no dhcpcd processes before these
statements and four processes afterwards.


--
Andy Richardson

We need Linux, like dolphins need a hole in the head.

Andy Richardson wrote:
> Trygve Selmer wrote:
> > If you run Slackware, which version ? Normally, rc.inet1 will start
>
>> dhcpcd if you don't assign any static ip (in rc.inet1 or rc.inet1.conf
>> depending on Slackware version). Why did you insert the extra stuff in
>> rc.inet1 ?
>
> The extra stuff was just to prove to myself by watching the screen
> during boot up that there were no dhcpcd processes before these
> statements and four processes afterwards.

Yes, but what distribution are you running ? Hard to tell what's going
on without any real information.

> Yes, but what distribution are you running ? Hard to tell what's going
> on without any real information.

I'm running Vectorlinux4.0 which is apparently based on Slackware -
though it seems you had already spotted that.

Your interest in the startup scripts has given me some ideas. I have met
some similar 'quirks' when setting up a DHCP server on the same network.

So , I'm off to spend the afternoon getting acquainted with the startup
scripts. It seems that some files are left over from the distribution
maintainer's original slackware setup and their own box. (some stuff is
never called and some is called twice from different places.)

It may just be some odd case statements in the scripts falling through
and calling the daemon twice.

I know Vectorlinux4.0 is at least 4 years old but it runs on my 4x
Pentium 166 machines with 32-64M ram.
So obviously nothing mission critical here ;-)


--
Andy Richardson

We need Linux, like dolphins need a hole in the head.