On Tue, 1 Aug 2006, Amit Gud wrote:
/etc/sysctl.conf values are of no use to kernel modules that are inserted
after init scripts call sysctl for the values in /etc/sysctl.conf
For modules to use the values stored in the file /etc/sysctl.conf, sysctl
kernel code can keep record of 'limited' values, for sysctl entries which
haven't been registered yet. During registration, sysctl code can check
against the stored values and call the appropriate strategy and proc_handler
routines if a match is found.
Attached patch does just that. This patch is NOT tested and is just to get
opinions, if something like this is a right way of addressing this problem.
Do you anticipate any users that you could list? It seems like a more
appropriate approach would be to allow some kind of user-space hook or
event notification to run upon module insertion, which could then apply
the appropriate sysctl.
Thanks,
AG
Thanks,
Chase
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]