All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Tim Hockin <thockin@hockin.org>,
	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 19:11:31 +1100	[thread overview]
Message-ID: <20040121081430.004AA2C10D@lists.samba.org> (raw)
In-Reply-To: Your message of "Wed, 21 Jan 2004 15:14:03 +1100." <400DFC8B.7020906@cyberone.com.au>

In message <400DFC8B.7020906@cyberone.com.au> you write:
> Or doesn't anybody care to think about hoplug scripts failing?
> (serious question)

It seems not.  I don't neccessarily agree with it, but we'll see how
it goes.

Guarantees are hard: if the script is supposed to fork something and
you're out of memory, what do you do?

Cheers,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  parent reply	other threads:[~2004-01-21  8:14 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
2004-01-21  7:42                                 ` Tim Hockin
2004-01-21  8:11                             ` Rusty Russell [this message]
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=20040121081430.004AA2C10D@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    --cc=rml@tech9.net \
    --cc=rusty@au1.ibm.com \
    --cc=thockin@hockin.org \
    --cc=torvalds@osdl.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.