dhcpcd-discuss

Re: blank resolv.conf

Roy Marples

Tue Nov 10 11:23:45 2020

On 10/11/2020 11:18, Jan Pohanka wrote:
188 root     dhcpcd eth0

Do you please have an idea what could start this process?

Anything could start this process.

> $ ps | grep dh
> 188 root     dhcpcd eth0
> 215 root     /sbin/dhcpcd -f /etc/dhcpcd.conf
>
> Is it a problem? One of the instances is started by an init.d script
> provided by a buildroot package. The second one probably by ifup
> scripts, but I do not see it now. I have to search...
>

So you've already said where you should look.

If I had to guess you have a network init script which calls ifup.
Let us assume it's Debian's ifup so look in /etc/network/interfaces and check if you have set eth0 to dhcp.

IF so, I would remove this and set it to static or anything other than auto.

Then let the other init.d script start dhcpcd on all interfaces as it's currently doing.

OR do it the other way around - disable the init script that's starting dhcpcd in master mode and let ifup do it. This is worse than the former, but if you only ever have one interface then it doesn't matter.

Roy

Follow-Ups:
Re: blank resolv.confJan Pohanka
References:
blank resolv.confJan Pohanka
Re: blank resolv.confRoy Marples
Re: blank resolv.confJan Pohanka
Re: blank resolv.confRoy Marples
Re: blank resolv.confJan Pohanka
Re: blank resolv.confJan Pohanka
Re: blank resolv.confRoy Marples
Re: blank resolv.confJan Pohanka
Re: blank resolv.confRoy Marples
Re: blank resolv.confJan Pohanka
Archive administrator: postmaster@marples.name