On Tue, Nov 20, 2012 at 1:52 AM, Lennart Poettering <lenn...@poettering.net> wrote: > B1;3401;0cOn Tue, 20.11.12 01:33, Kay Sievers (k...@vrfy.org) wrote: > >> >> On Tue, Nov 20, 2012 at 1:06 AM, Lennart Poettering >> <lenn...@poettering.net> wrote: >> > On Mon, 19.11.12 08:13, Mantas Mikulėnas (graw...@gmail.com) wrote: >> >> >> This doesn't affect TCPCongestion= in systemd socket units, since root >> >> is allowed to set any algorithm, and the module is simply loaded on >> >> demand when systemd asks for it... >> >> >> >> How can this be fixed? >> > >> > Hmm, whenever a module is loaded this also generates udev events, maybe >> > for this specific case we should add a udev rule that tries to write the >> > sysctl again after the module was successfully loaded? >> >> Sounds kinda scary, and is probably too simple. We always run coldplug >> for all modules, at every bootup, and they will all run parallel, >> doing all the same apply sysctl over and overfor all devices ... > > I was suggesting a rule only for that one specific module where this is > useful...
Yeah, but playing catch-up with all the kernel module names in userspace rules is getting out of control pretty soon. Hmm, and we still have to solve the problem of applying that stuff only once, I guess, and not for all modules in that list that would start executing the same tool in parallel. Kay _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
