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

Michael Biebl biebl at debian.org
Thu Dec 15 23:27:10 GMT 2016


On Thu, 31 Mar 2016 16:45:40 +0200 Martin Mares <mj at ucw.cz> 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
> > interfaces, is started after systemd-sysctl.service.
> 
> On my system (Wheezy recently upgraded to Jessie):
> 
> | ● networking.service - LSB: Raise network interfaces.
> |    Loaded: loaded (/etc/init.d/networking)
> |   Drop-In: /run/systemd/generator/networking.service.d
> |            └─50-insserv.conf-$network.conf
> |         /lib/systemd/system/networking.service.d
> |            └─network-pre.conf
> |    Active: active (exited) since Sun 2016-03-20 21:56:51 CET; 1 weeks 3 days ago
> 
> /run/systemd/generator/networking.service.d/50-insserv.conf-$network.conf
> contains only:
> 
> | # Automatically generated by systemd-insserv-generator
> | 
> | [Unit]
> | Wants=network.target
> | Before=network.target
> 
> /lib/systemd/system/networking.service.d/network-pre.conf contains only:
> 
> | [Unit]
> | After=network-pre.target
> 
> No trace of systemd-sysctl.service anywhere.
> 
> > And for hotplugged devices
> > 
> > /lib/udev/rules.d/99-systemd.rules contains
> > > 99-systemd.rules:# Apply sysctl variables to network devices (and only to those) as they appear.
> > > 99-systemd.rules:ACTION=="add", SUBSYSTEM=="net", KERNEL!="lo", RUN+="/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/$name --prefix=/net/ipv4/neigh/$name --prefix=/net/ipv6/conf/$name --prefix=/net/ipv6/neigh/$name"
> 
> This works for per-interface options, but not for /net/ipv6/conf/default.
> (However, I probably should abandon using conf/default anyway, since some
> kernel modules are loaded before sysctl is set.)
> 
>

Afaics, this is fixed in stretch.
systemd-networkd.service has After=systemd-sysctl.service, so does
ifup at .service and networking.service.

So, question is what to do about this in jessie.
We already ship
/lib/systemd/system/networking.service.d/network-pre.conf in systemd,
containing
[Unit]
After=network-pre.target

We could extend that to include After=systemd-sysctl.service.

It would be cleaner if that was shipped in ifupdown itself, but in
jessie, systemd also provides ifup at .service. Both were mistakes in
hindsight, which I'm not sure is worth fixing retroactively.

Guus, do you have any preference here. Do you want to take over that
file from systemd and make a jessie stable upload?
If not, I'd add the After ordering to the jessie systemd package.

Let me know what you think.

Regards,
Michael




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20161216/094d8179/attachment.sig>


More information about the Pkg-systemd-maintainers mailing list