Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #178644
| From | <tomas@tuxteam.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Why 2 dhclient processes running for eth0 (IPv4)? |
| Date | 2017-03-10 14:30 +0100 |
| Message-ID | <tjsMh-4Ar-11@gated-at.bofh.it> (permalink) |
| References | <tiEcN-38Q-13@gated-at.bofh.it> <tjqr7-2Qu-3@gated-at.bofh.it> <tjsMh-4Ar-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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). Regards - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAljCqZwACgkQBcgs9XrR2kYLlACfWY3HLojGwlC9Wsa2+TnUzjVW micAn3mgTQaOTBfpp3NqZ/vFkZUTQ77A =bPJL -----END PGP SIGNATURE-----
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Why 2 dhclient processes running for eth0 (IPv4)? Clark Wang <dearvoid@gmail.com> - 2017-03-08 08:30 +0100
Re: Why 2 dhclient processes running for eth0 (IPv4)? Clark Wang <dearvoid@gmail.com> - 2017-03-10 12:00 +0100
Re: Why 2 dhclient processes running for eth0 (IPv4)? <tomas@tuxteam.de> - 2017-03-10 12:40 +0100
Re: Why 2 dhclient processes running for eth0 (IPv4)? <tomas@tuxteam.de> - 2017-03-10 14:40 +0100
Re: Why 2 dhclient processes running for eth0 (IPv4)? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-03-10 14:40 +0100
Re: Why 2 dhclient processes running for eth0 (IPv4)? <tomas@tuxteam.de> - 2017-03-10 14:30 +0100
Re: Why 2 dhclient processes running for eth0 (IPv4)? Jonathan Dowland <jmtd@debian.org> - 2017-03-10 14:30 +0100
Re: Why 2 dhclient processes running for eth0 (IPv4)? Clark Wang <dearvoid@gmail.com> - 2017-03-13 06:10 +0100
csiph-web