> Could it be that something about keeping daemons started during ifup
running be accidentally dropped?
Not that I know of, and in my wily VMs dhclient runs happily.
I don't know whether ifupdown has some useful debugging facilities. I
tried adding /usr/bin/strace -fvvs1024 -o /run/ifup.trace to
/etc/init.d/networking, but it doesn't give much information (in
particular, it doesn't end up calling dhclient). Do you get anything
useful if you set VERBOSE=yes in /etc/default/networking and reboot?
(Please attach journal again)
** Package changed: ubuntu => ifupdown (Ubuntu)
** Changed in: ifupdown (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466790
Title:
dhclient does not remain running on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1466790/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
