| 1 |
On Sep 12, 2013 8:04 AM, "Stefan G. Weichinger" <lists@×××××.at> wrote: |
| 2 |
> |
| 3 |
> Am 12.09.2013 14:43, schrieb Mick: |
| 4 |
> |
| 5 |
> >> I don't have that binary. And some page on my way said the |
| 6 |
> >> contrary: set it to empty and let udev (?) do that. |
| 7 |
> > |
| 8 |
> > Ha! Neither do I! |
| 9 |
> > |
| 10 |
> > # ls -la /sbin/hotplug ls: cannot access /sbin/hotplug: No such |
| 11 |
> > file or directory |
| 12 |
> > |
| 13 |
> > I can honestly say that I can't remember filling in this entry when |
| 14 |
> > configuring my kernels, but then how did it get there? |
| 15 |
> > |
| 16 |
> |
| 17 |
> dunno. |
| 18 |
> |
| 19 |
> Kernel help says about that setting: |
| 20 |
> |
| 21 |
> > Before the switch to the netlink-based uevent source, this was |
| 22 |
> > │ │ used to hook hotplug scripts into kernel device events. It |
| 23 |
> > │ │ usually pointed to a shell script at /sbin/hotplug. |
| 24 |
> > │ │ This should not be used today, because usual systems create |
| 25 |
> > │ │ many events at bootup or device discovery in a very short time |
| 26 |
> > │ │ frame. One forked process per event can create so many |
| 27 |
> > processes |
| 28 |
> > │ │ that it creates a high system load, or on smaller systems |
| 29 |
> > │ │ it is known to create out-of-memory situations during bootup. |
| 30 |
> |
| 31 |
> |
| 32 |
> I also found configs having this: |
| 33 |
> |
| 34 |
> CONFIG_UEVENT_HELPER_PATH="/usr/bin/udevadm" |
| 35 |
> |
| 36 |
> That binary would exist here. |
| 37 |
> |
| 38 |
> I am unsure if I should try that. |
| 39 |
|
| 40 |
Don't, that only will create potential fork bombs. |
| 41 |
|
| 42 |
Regards. |
Archives