From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] uevent_helper on kernel 3.16.5-gentoo
Date: Fri, 24 Oct 2014 12:47:14 +0100 [thread overview]
Message-ID: <20141024124714.319e4ec1@hactar.digimed.co.uk> (raw)
In-Reply-To: <201410241237.10235.michaelkintzios@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
On Fri, 24 Oct 2014 12:36:44 +0100, Mick wrote:
> I understand that udev needs or used to need uevent_helper, but I am
> not clear if I should or should not enable this module in a new kernel
> I'm rolling. Can you please advise:
>
>
> CONFIG_UEVENT_HELPER:
>
> The uevent helper program is forked by the kernel for
> every uevent.
> Before the switch to the netlink-based uevent source, this was
> used to hook hotplug scripts into kernel device events. It
> usually pointed to a shell script at /sbin/hotplug.
> This should not be used today,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> because usual systems create
> many events at bootup or device discovery in a very short time
> frame. One forked process per event can create so many processes
> that it creates a high system load, or on smaller systems
> it is known to create out-of-memory situations during bootup.
It's a legacy setting, introduced so you can turn off this feature.
Presumably it defaults to Y for compatibility but I've been following the
advice and running without it for some time now - on desktops and servers.
--
Neil Bothwick
WinErr 004: Erroneous error - Nothing is wrong
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-10-24 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 11:36 [gentoo-user] uevent_helper on kernel 3.16.5-gentoo Mick
2014-10-24 11:47 ` Neil Bothwick [this message]
2014-10-24 12:06 ` Mick
2014-10-24 14:13 ` Douglas J Hunley
2014-10-24 14:44 ` Mick
2014-10-27 13:40 ` Douglas J Hunley
2014-10-27 15:10 ` Mick
2014-10-28 12:57 ` Douglas J Hunley
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=20141024124714.319e4ec1@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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