From: Frederik Deweerdt <deweerdt@free.fr>
To: Amit Gud <agud@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] sysctl for the latecomers
Date: Tue, 1 Aug 2006 17:25:03 +0200 [thread overview]
Message-ID: <20060801152503.GA2825@slug> (raw)
In-Reply-To: <44CF69F0.6040801@redhat.com>
On Tue, Aug 01, 2006 at 10:49:20AM -0400, 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.
>
>
Hi,
One strange behaviour that comes to mind is the following:
1. I boot my machine so that it doesn't load module X
2. I modify /etc/sysctl.conf and I remove a line affecting module X
3. I modprobe X
Wouldn't the fact that the sysctl directive is applied anyway be a bit
misleading?
Regards,
Frederik
next prev parent reply other threads:[~2006-08-01 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 14:49 [RFC] [PATCH] sysctl for the latecomers Amit Gud
2006-08-01 15:25 ` Frederik Deweerdt [this message]
2006-08-01 16:56 ` Chase Venters
2006-08-01 17:22 ` Chase Venters
2006-08-01 19:04 ` Amit Gud
2006-08-01 20:36 ` Chase Venters
2006-08-02 14:56 ` Horst H. von Brand
2006-08-01 17:41 ` H. Peter Anvin
2006-08-01 18:54 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060801152503.GA2825@slug \
--to=deweerdt@free.fr \
--cc=agud@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox