From: Nick Piggin <piggin@cyberone.com.au>
To: Tim Hockin <thockin@hockin.org>
Cc: vatsa@in.ibm.com, Rusty Russell <rusty@au1.ibm.com>,
linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org,
rml@tech9.net
Subject: Re: CPU Hotplug: Hotplug Script And SIGPWR
Date: Wed, 21 Jan 2004 18:31:06 +1100 [thread overview]
Message-ID: <400E2ABA.2060809@cyberone.com.au> (raw)
In-Reply-To: <20040121070939.GB31807@hockin.org>
Tim Hockin wrote:
>On Wed, Jan 21, 2004 at 03:14:03PM +1100, Nick Piggin wrote:
>
>>Or doesn't anybody care to think about hoplug scripts failing?
>>(serious question)
>>
>
>If hotplug scripts are failing, you're in really deep trouble. I can't find
>a single case where a hotplug script failing would not indicate some other
>larger failure.
>
sigh. threads-max, pid_max, ulimit, -ENOMEM, oom.
In my opinion, you can be in fine shape after one of the above happening,
and if limits _are_ in place, its reasonable to expect they're there because
they might get reached in rare cases.
I'd rather not add something that, by design can hang any number of
processes
including the entire system if a hotplug script fails. Thats just my honest
opinion, I know its rare enough it probably would never happen to anyone.
Sorry I keep repeating this, its not my call and its never going to affect
me so I'll shut up now ;)
next prev parent reply other threads:[~2004-01-21 7:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040116174446.A2820@in.ibm.com>
2004-01-20 5:44 ` CPU Hotplug: Hotplug Script And SIGPWR Rusty Russell
2004-01-20 6:33 ` Tim Hockin
2004-01-20 6:43 ` Nick Piggin
2004-01-20 6:52 ` Tim Hockin
2004-01-20 7:11 ` Nick Piggin
2004-01-20 7:30 ` Tim Hockin
2004-01-20 7:45 ` Nick Piggin
2004-01-20 7:54 ` Tim Hockin
2004-01-20 8:14 ` Nick Piggin
2004-01-20 8:29 ` Tim Hockin
2004-01-20 8:37 ` Nick Piggin
2004-01-20 8:43 ` Tim Hockin
2004-01-21 4:06 ` Srivatsa Vaddagiri
2004-01-21 4:14 ` Nick Piggin
2004-01-21 5:09 ` Srivatsa Vaddagiri
2004-01-21 7:08 ` Tim Hockin
2004-01-21 15:07 ` Matthias Urlichs
2004-01-22 5:29 ` Rusty Russell
2004-01-21 7:09 ` Tim Hockin
2004-01-21 7:31 ` Nick Piggin [this message]
2004-01-21 7:42 ` Tim Hockin
2004-01-21 8:11 ` Rusty Russell
2004-01-21 5:07 ` Rusty Russell
2004-01-20 8:41 ` Stefan Smietanowski
2004-01-20 8:49 ` Nick Piggin
2004-01-20 9:12 ` Tim Hockin
2004-01-21 0:00 ` Rusty Russell
2004-01-20 23:51 ` Rusty Russell
2004-01-20 7:45 ` Rusty Russell
2004-01-20 8:37 ` Tim Hockin
2004-01-20 9:29 ` Srivatsa Vaddagiri
2004-01-21 0:12 ` Rusty Russell
[not found] <fa.f37o48p.1io5q5@ifi.uio.no>
[not found] ` <fa.frjqvfo.170g8hq@ifi.uio.no>
2004-01-20 17:49 ` Andy Lutomirski
2004-01-21 4:33 ` Rusty Russell
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=400E2ABA.2060809@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=rusty@au1.ibm.com \
--cc=thockin@hockin.org \
--cc=torvalds@osdl.org \
--cc=vatsa@in.ibm.com \
/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