From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2D17E1381F3 for ; Thu, 12 Sep 2013 15:11:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 03252E0CB5; Thu, 12 Sep 2013 15:11:16 +0000 (UTC) Received: from mail-lb0-f171.google.com (mail-lb0-f171.google.com [209.85.217.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D24A0E0C68 for ; Thu, 12 Sep 2013 15:11:14 +0000 (UTC) Received: by mail-lb0-f171.google.com with SMTP id u14so1024588lbd.16 for ; Thu, 12 Sep 2013 08:11:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=8ChNqEE5kI3PPq1iXrcVg7pHjBaTJDrkxeif0tKv/fo=; b=snDQOxt37r/Sm67FiaBmHmYMAbNJQ8MDXVdh3p8TcxVTR1+JUZWb3VSUqBha58HTD9 QbcM+a3r4HrJgYGu0/RO2EyNQBAsSxvw4VzSaWIdt2gFrCmRvVf3TppdBgoONU9/jnT/ nMjMm2JSlDzQ3gzRHuZmys7Hz9YGVeRZnFLBGeg1eoyf0OMqHkjO/71I3ITFB9t366Sh NtptF3d+vKV00W03HofVxqy6GwDBh6x0LV4xznPllrHWgGExsdpgK9sMO2HK1lKdIfmW fgyTjC012adPO1aVZuh32XASbbFcHyYGo/UJ/v3bDWTiPyQe1rtV7Ugjx9lp11czydVh V4Ew== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.112.156.103 with SMTP id wd7mr624294lbb.48.1378998673100; Thu, 12 Sep 2013 08:11:13 -0700 (PDT) Received: by 10.114.96.2 with HTTP; Thu, 12 Sep 2013 08:11:13 -0700 (PDT) Received: by 10.114.96.2 with HTTP; Thu, 12 Sep 2013 08:11:13 -0700 (PDT) In-Reply-To: <5231BBBA.5020005@xunil.at> References: <5230528A.4080302@xunil.at> <201309120751.13625.michaelkintzios@gmail.com> <52317D4C.7080903@xunil.at> <201309121344.04168.michaelkintzios@gmail.com> <5231BBBA.5020005@xunil.at> Date: Thu, 12 Sep 2013 10:11:13 -0500 Message-ID: Subject: Re: [gentoo-user] systemd and lvm From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=089e011609380e53a704e63126dc X-Archives-Salt: f07fd049-deb3-43d0-94eb-d4899116b3e7 X-Archives-Hash: 5e81af51ab41f5abe256f82b50e6b9c5 --089e011609380e53a704e63126dc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sep 12, 2013 8:04 AM, "Stefan G. Weichinger" wrote: > > Am 12.09.2013 14:43, schrieb Mick: > > >> I don't have that binary. And some page on my way said the > >> contrary: set it to empty and let udev (?) do that. > > > > Ha! Neither do I! > > > > # ls -la /sbin/hotplug ls: cannot access /sbin/hotplug: No such > > file or directory > > > > I can honestly say that I can't remember filling in this entry when > > configuring my kernels, but then how did it get there? > > > > dunno. > > Kernel help says about that setting: > > > Before the switch to the netlink-based uevent source, this was > > =E2=94=82 =E2=94=82 used to hook hotplug scripts into kernel device eve= nts. It > > =E2=94=82 =E2=94=82 usually pointed to a shell script at /sbin/hotplug. > > =E2=94=82 =E2=94=82 This should not be used today, because usual system= s create > > =E2=94=82 =E2=94=82 many events at bootup or device discovery in a very= short time > > =E2=94=82 =E2=94=82 frame. One forked process per event can create so m= any > > processes > > =E2=94=82 =E2=94=82 that it creates a high system load, or on smaller s= ystems > > =E2=94=82 =E2=94=82 it is known to create out-of-memory situations duri= ng bootup. > > > I also found configs having this: > > CONFIG_UEVENT_HELPER_PATH=3D"/usr/bin/udevadm" > > That binary would exist here. > > I am unsure if I should try that. Don't, that only will create potential fork bombs. Regards. --089e011609380e53a704e63126dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Sep 12, 2013 8:04 AM, "Stefan G. Weichinger" <lists@xunil.at> wrote:
>
> Am 12.09.2013 14:43, schrieb Mick:
>
> >> I don't have that binary. =C2=A0And some page on my way s= aid the
> >> contrary: set it to empty and let udev (?) do that.
> >
> > Ha! =C2=A0Neither do I!
> >
> > # ls -la /sbin/hotplug ls: cannot access /sbin/hotplug: No such > > file or directory
> >
> > I can honestly say that I can't remember filling in this entr= y when
> > =C2=A0configuring my kernels, but then how did it get there?
> >
>
> dunno.
>
> Kernel help says about that setting:
>
> > Before the switch to the netlink-based uevent source, this was > > =E2=94=82 =E2=94=82 used to hook hotplug scripts into kernel devi= ce events. It
> > =E2=94=82 =E2=94=82 usually pointed to a shell script at /sbin/ho= tplug.
> > =E2=94=82 =E2=94=82 This should not be used today, because usual = systems create
> > =E2=94=82 =E2=94=82 many events at bootup or device discovery in = a very short time
> > =E2=94=82 =E2=94=82 frame. One forked process per event can creat= e so many
> > processes
> > =E2=94=82 =E2=94=82 that it creates a high system load, or on sma= ller systems
> > =E2=94=82 =E2=94=82 it is known to create out-of-memory situation= s during bootup.
>
>
> I also found configs having this:
>
> CONFIG_UEVENT_HELPER_PATH=3D"/usr/bin/udevadm"
>
> That binary would exist here.
>
> I am unsure if I should try that.

Don't, that only will create potential fork bombs.

Regards.

--089e011609380e53a704e63126dc--