Bug#819314: procps: [sysctl] Missing dependency when used with systemd

2016-12-16 Thread Guus Sliepen
On Fri, Dec 16, 2016 at 12:27:10AM +0100, Michael Biebl wrote: > It would be cleaner if that was shipped in ifupdown itself, but in > jessie, systemd also provides ifup@.service. Both were mistakes in > hindsight, which I'm not sure is worth fixing retroactively. > > Guus, do you have any

Bug#819314: procps: [sysctl] Missing dependency when used with systemd

2016-12-15 Thread Michael Biebl
Am 16.12.2016 um 00:27 schrieb Michael Biebl: > Afaics, this is fixed in stretch. > systemd-networkd.service has After=systemd-sysctl.service, so does > ifup@.service and networking.service. The relevant commits in ifupdown are

Bug#819314: procps: [sysctl] Missing dependency when used with systemd

2016-12-15 Thread Michael Biebl
On Thu, 31 Mar 2016 16:45:40 +0200 Martin Mares wrote: > Hello! > > > Are you sure? > > networking.service has > > > After=local-fs.target network-pre.target apparmor.service > > > systemd-sysctl.service > > > > This makes sure that networking.service, which deals with type auto >

Bug#819314: procps: [sysctl] Missing dependency when used with systemd

2016-03-31 Thread Martin Mares
Hello! > Are you sure? > networking.service has > > After=local-fs.target network-pre.target apparmor.service > > systemd-sysctl.service > > This makes sure that networking.service, which deals with type auto > interfaces, is started after systemd-sysctl.service. On my system (Wheezy recently