Re: Why 2 dhclient processes running for eth0 (IPv4)?
- Date: Fri, 10 Mar 2017 14:26:52 +0100
- From: <tomas@xxxxxxxxxx>
- Subject: Re: Why 2 dhclient processes running for eth0 (IPv4)?
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, Mar 10, 2017 at 01:23:36PM +0000, Jonathan Dowland wrote:
> On Fri, Mar 10, 2017 at 06:58:30PM +0800, Clark Wang wrote:
> > > There are 2 `dhclient` processes running for `eth0` (IPv4). Rebooting does
> > > not help for me.
> > >
> > Anyone else has the same problem?
> I think I have sometimes seen this, but I do not know what provokes it. The most
> likely explanation is installing more than one network management system and/or
> leaving more than one configured. So for example I have had ifupdown and wicd both
> attempt to manage interfaces.
> If you look at the parent PID for the dhclient instances, you might get some clues.
> (ps -eaf --forest for example, or pstree(1))
I was tempted to propose that too, but mine daemonizes and becomes
init's child (ifupdown, don't know what other network managers do).
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----