[systemd-devel] "sysctl.conf" applied too late

Reindl Harald h.reindl at thelounge.net
Wed Feb 8 08:00:31 PST 2012

Am 08.02.2012 16:40, schrieb Lennart Poettering:
> On Wed, 08.02.12 16:07, Reindl Harald (h.reindl at thelounge.net) wrote:
>> can someone please take a look at this
>> in myopinion it is not optimal starting services which
>> possibly read settings controlled by "systcl.conf"
>> and after that the local settings get applied
>> sample below:
>> after boot smbd is listening on ipv6, sysctl disables this,
>> but seems to do it after smbd has started, manual restarting
>> the service stops smbd to listen on ipv6
>> this may also problematic for all sort of software
> 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"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20120208/d03f8caf/attachment.pgp>

More information about the systemd-devel mailing list