Re: future of sysctls?

[Ludwig Nussel <ludwig.nussel@suse.de>]

Lennart Poettering wrote:
> On Tue, 17.05.11 09:15, Ludwig Nussel (ludwig.nussel@suse.de) wrote:
> > Lennart Poettering wrote:
> > > On Thu, 12.05.11 17:41, Ludwig Nussel (ludwig.nussel@suse.de) wrote:
> > > > I'm currently struggling to find a sane way to set
> > > > net.ipv6.conf.default.use_tempaddr.
> > > > Traditionally at some point during boot "sysctl -e -q -p /etc/sysctl.conf" is
> > > > called. That doesn't really work out anymore. The aforementioned setting needs
> > > > to be applied after the ipv6 module is loaded (could be compiled into the
> > > > kernel too though) otherwise it wouldn't apply. It needs to be set before a
> > > > network driver is loaded though as the default value is copied to
> > > > interfaces specific settings at interface creation time. On top of
> > > > that there are also network interface specific sysctls that need to
> > > > be applied after an interface is created (e.g.
> > > > net.ipv6.conf.eth0.use_tempaddr).
> > > 
> > > Something like this is kinda broken anyway, since it is racy: you can
> > > apply the sysctl only after the interface is already available.
> > 
> > Exactly.
> > 
> > > Might be a good idea to just ignore these kinds of settings. Or if this
> > > is not possible, then set them from NM or whatever controls the network.
> > 
> > That's that hack that's currently in place. Network scripts grep
> > /etc/sysctl.conf for interface specific settings...
> 
> Urks. What we could do to make this nicer is add a simple prefix match
> logic to our sysctl apply tool, so that it is easy to apply a subtree of
> sysctls when the time comes.

I've sent a patch to the procps maintainer but he has yet to
respond. It's not a real solution anyways. It just makes a dirty
hack a little more efficient.

cu
Ludwig

-- 
 (o_   Ludwig Nussel
 //\
 V_/_  http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)