#535732 warning: There is already a pid file /var/run/dhclient.eth0.pid

Package:
ifupdown
Source:
ifupdown
Description:
high level tools to configure network interfaces
Submitter:
Martin Geisler
Date:
2015-09-05 20:48:27 UTC
Severity:
minor
#535732#5
Date:
2009-07-04 17:07:14 UTC
From:
To:
I get a warning like this every time I shutdown my computer:

  Deconfiguring network interfaces... There is already a pid file
  /var/run/dhclient.eth0.pid with pid 4000

It is harmless in itself, but it annoying to get such a warning (in
red letters) on every shutdown.
#535732#10
Date:
2010-03-17 13:29:30 UTC
From:
To:
Any updates?
It's still annoying...

I'd actually prefer DHCP to not do anything on shutdown.
#535732#15
Date:
2010-06-16 10:35:28 UTC
From:
To:
Somebody?
#535732#20
Date:
2010-06-16 17:13:49 UTC
From:
To:
I'm focusing on the 4.1 packages at the moment, which I plan on uploading to
unstable as soon as the release team tells me I can. I don't believe this
bug is present there. Have you tried testing the packages in experimental?
#535732#25
Date:
2010-06-16 21:29:02 UTC
From:
To:
The warning is gone. The output is still very verbose though.
Is it necessary to run dhcp at shutdown at all?

Olaf
#535732#30
Date:
2010-06-16 22:40:47 UTC
From:
To:
Is it? I'd found running it manually that it was totally silent without a -v
option (-q is now implied)

Quite possibly not, but I've been struggling to get the package to upgrade
without warnings from update-rc.d. It's a work in progress.
#535732#35
Date:
2010-06-16 23:03:41 UTC
From:
To:
Yes, see screenshot.

Olaf
#535732#40
Date:
2010-06-16 23:16:57 UTC
From:
To:
This issue is with how ifup/ifdown is invoking dhclient (as opposed to
dhclient3). It's passing a -v for dhclient (but not for dhclient3).

I'll take this up with the ifupdown maintainer
#535732#45
Date:
2010-06-16 23:18:54 UTC
From:
To:
Ah, it was intentional for consistency:

ifupdown (0.6.8+nmu3) unstable; urgency=low

  * Non-maintainer upload. (with maintainer's consent)
  * Correctly make the modification in 0.6.8+nmu2
  * Also adjust the way /sbin/dhclient is killed to be comparable to how
    /sbin/dhclient is stopped
  * Invoke dhclient with -v to maintain equivalent verbosity to dhclient3
  * Conflict with dhcp-client v2
#535732#50
Date:
2010-06-17 11:46:05 UTC
From:
To:
I think it's better to decrease the verbosity (if not avoiding DHCP
release at all).

Olaf