Hey Alex, Alex Mayer [2015-07-17 13:53 +0000]: > If network is off, on some systems, [email protected] fails. > Which is not that bad, but still unnecessary. > systemctl status -l [email protected] > ● [email protected] - ifup for eth0 > Loaded: loaded (/lib/systemd/system/[email protected]; static; vendor preset: > enabled) > Active: failed (Result: exit-code) since Fr 2015-07-17 13:33:51 CEST; > 1min 17s ago > Process: 730 ExecStop=/sbin/ifdown %I (code=exited, status=0/SUCCESS) > Process: 687 ExecStartPost=/sbin/ifquery --state %I (code=exited, > status=1/FAILURE) > Process: 686 ExecStart=/sbin/ifup --allow=hotplug %I (code=killed, > signal=TERM) > Main PID: 686 (code=killed, signal=TERM)
That's intended -- if ifup fails to bring up the interface, the unit is *supposed* to fail; that's the very reason for that ExecStartPost command. But you don't get any delays any more, right? Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
