From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] uevent_helper on kernel 3.16.5-gentoo
Date: Fri, 24 Oct 2014 12:36:44 +0100 [thread overview]
Message-ID: <201410241237.10235.michaelkintzios@gmail.com> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 1046 bytes --]
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.
Symbol: UEVENT_HELPER [=y]
Type : boolean
Prompt: Support for uevent helper
Location:
-> Device Drivers
-> Generic Driver Options
Defined at drivers/base/Kconfig:3
Support for uevent helper (UEVENT_HELPER) [Y/n/?] (NEW)
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2014-10-24 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 11:36 Mick [this message]
2014-10-24 11:47 ` [gentoo-user] uevent_helper on kernel 3.16.5-gentoo Neil Bothwick
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=201410241237.10235.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--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