On Dec 26, Guus Sliepen <g...@debian.org> wrote:

> Hm, that sounds like a bug in systemd or in some other component that it
> calls during "systemctl enable networking.service". Marco, can you see
> from your strace logs what process did that dbus call?
Just "systemctl enable networking.service".

> The current version of ifupdown calls systemctl from postinst "by hand",
> but the next version will use dh-systemd, maybe that will fix this issue
> as well, but I'm not sure.
The problem is that networking.service is already enabled (by insserv), 
but I expected the command to be idempotent anyway:

● networking.service - Raise network interfaces
   Loaded: loaded (/usr/lib/systemd/system/networking.service; enabled; vendor 
preset: enabled)
  Drop-In: /run/systemd/generator/networking.service.d
           └─50-insserv.conf-$network.conf
        /usr/lib/systemd/system/networking.service.d
           └─systemd.conf
   Active: active (exited) since Sun 2015-10-25 13:48:55 CET; 2 months 1 days 
ago

root@bongo:~# cat 
/usr/lib/systemd/system/networking.service.d/systemd.conf 
[Unit]
After=network-pre.target apparmor.service
root@bongo:~#

-- 
ciao,
Marco

Attachment: signature.asc
Description: PGP signature

Reply via email to