[systemd-devel] "sysctl.conf" applied too late
lennart at poettering.net
Wed Feb 8 08:06:17 PST 2012
On Wed, 08.02.12 17:00, Reindl Harald (h.reindl at thelounge.net) wrote:
> > Hmm, so we actually apply sysctls very early in the boot, and we do not
> > spawn normal services before this finished. There's one exception
> > however: settings on network interfaces are applied as the network
> > interfaces show up, but before the udev event for them showing up is
> > send to the applications. That means that any app running in the normal
> > start-up phase and/or using udev to listen for network interfaces
> > showing up should see sysctls only fully applied.
> > There must be something else going wrong here?
> wild guess: services not have "network.target" as Before/After defined an bind on
> all avaiable interfaces? this would explained with "settings on network interfaces
> are applied as the network interfaces show up"
Hmm, so what makes me wonder here: which sysctls are this actually?
NM uses udev to detect when the ifaces show up, so I'd assume we are
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel