linux-kernel - Re: Changing sysctl values within the kernel?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200611270940.40792.dj@david-web.co.uk>
Date:	Mon, 27 Nov 2006 09:40:40 +0000
From:	David Johnson <dj@...id-web.co.uk>
To:	Alexey Dobriyan <adobriyan@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Changing sysctl values within the kernel?

On Sunday 26 November 2006 20:38, you wrote:
> On Sat, Nov 25, 2006 at 07:11:48PM +0000, David Johnson wrote:
> >
> > Is there an accepted way of setting sysctl values within the kernel (I
> > can't seem to find any other module doing this),
>
> Yes. Next in-kernel module changing sysctls will do it via
>
> 	stop_a_enabled = 1;
> 	console_loglevel = 8;
>
> (be sure, variables in question are EXPORT_SYMBOL'ed)
>

Bah, I never thought it would be that simple!

>
> > Would it perhaps be better to instead create a sysfs node and let a
> > userspace daemon worry about setting the sysctl values?
>
> Now _this_ is silly. sysctls already live in /proc/sys/, so you can open(2)
> /proc/sys/kernel/printk and write(2) to it.

OK, I'll give that a miss then ;-)

Thanks for your help!

David.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/