From: Hannes Reinecke <hare@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug for klibc utils
Date: Fri, 27 Feb 2004 13:29:20 +0000 [thread overview]
Message-ID: <403F4630.1000203@suse.de> (raw)
In-Reply-To: <200402271402.06890.arnd@arndb.de>
Arnd Bergmann wrote:
> Several people have run into problems when attaching large disk arrays to
> a mainframe because of running /sbin/hotplug as a bash script takes far
> longer than the interval between hotplug events.
>
> Attaching more than 300 devices at once will cause an out-of-memory
> condition and the kernel starts killing random processes.
>
> Running only udev instead of hotplug from the kernel is fast enough.
>
> The shell version currently does:
>
>>DIR="/etc/hotplug.d"
>>for I in "${DIR}/$1/"*.hotplug "${DIR}/"default/*.hotplug ; do
>> if [ -f $I ]; then test -x $I && $I $1 ; fi
>>done
>>exit 1;
>
And so it does.
Just to double-check:
does this program also works for cases where the files in
/etc/hotplug.d/default
are scripts themselves?
Can't really see how this will help, since in that case we will have to
start bash anyway ... but what do I know ...
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux AG S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-02-27 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 13:02 hotplug for klibc utils Arnd Bergmann
2004-02-27 13:29 ` Hannes Reinecke [this message]
2004-02-27 13:53 ` Arnd Bergmann
2004-02-27 14:20 ` Hannes Reinecke
2004-02-27 16:52 ` Arnd Bergmann
2004-02-28 0:19 ` Greg KH
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=403F4630.1000203@suse.de \
--to=hare@suse.de \
--cc=linux-hotplug@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.