On 05/07/2010 10:19 AM, Andrea Ratto wrote:
It seems that the DHCP server does not reply to DHCPRELEASE so dhclient waits
until timeout.
My DSL modem does the same.
My workaround is to remove /etc/rc0.d/S35networking and
/etc/rc6.d/S35networking, but I would like to know if there is a way
Went ahead and modified /etc/init.d/networking to provide straces of the
ifdown command that is runs on a stop action.
running.png is a screen shot of my VM's normal output when running
`/etc/init.d/networking stop
shutdown.png is a screen shot of the same VM's shutdown logging.
running.strace
** Attachment added: running.png
http://launchpadlibrarian.net/47828206/running.png
--
dhclient3 hangs on shutdown
https://bugs.launchpad.net/bugs/571933
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
** Attachment added: shutdown.png
http://launchpadlibrarian.net/47828219/shutdown.png
--
dhclient3 hangs on shutdown
https://bugs.launchpad.net/bugs/571933
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
** Attachment added: running.strace
http://launchpadlibrarian.net/47828246/running.strace
--
dhclient3 hangs on shutdown
https://bugs.launchpad.net/bugs/571933
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
On 05/03/2010 07:23 AM, C de-Avillez wrote:
Thank you for opening this bug and helping make Ubuntu better. On Lucid
network startup/shutdown should be done via upstart (/etc/init/), not
via /etc/init.d.
Could you please give us logs for a shutdown with this issue?
** Changed in: dhcp3
I think my previous two comments really have nothing to do with the
actual problem. Me just grasping at straws trying to find some kind of
information. The following patch is a hack and not anywhere close to a
solution but does make the /etc/init.d/networking script complete during
shutdown.