Le 01/06/2014 10:52, Beck, Andre a écrit :
Hi,
I was affected by the same bug and found that resolvconf.service, while
loaded, was actually never run by systemd (jessie). Now I know nothing
about systemd and the bizarre maze of targets and services it comprises,
but it appeared to me that network.target might not be the ideal target
to use - it seemingly never triggers here. Maybe that's related to
NetworkManager (which stays absent from my system).
Hi !
You'r solution works for me.
For information, I was also affected by the problem although
network-manger is installed on my system, it seems not related with nm
dependencies.
Thanks !
--
Sébastien Dailly
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
