From: Werner Almesberger <wa@almesberger.net>
To: Krishna Kumar <kumarkr@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCHSET] Mobile IPv6 for 2.5.45
Date: Sat, 2 Nov 2002 23:23:08 -0300 [thread overview]
Message-ID: <20021102232308.A4482@almesberger.net> (raw)
In-Reply-To: <OFB7772DA2.01708E94-ON87256C65.006EDAE7@boulder.ibm.com>; from kumarkr@us.ibm.com on Sat, Nov 02, 2002 at 01:13:22PM -0800
[ Cc: trimmed ]
Krishna Kumar wrote:
> userspace - what happens when signals (KILL) are sent to that process ?
They die, as they should.
> We don't want the home agent functionality to stop in that case, even
> if it is a system admin error.
So what makes the home agent so much more important than, say, named,
pppd, gated, portmap, inetd, sendmail, sshd, etc. ?
A much more common admin mistake would be to reboot the wrong box, or
to disconnect the wrong cable, and you're powerless against this too.
If all else fails, add this to ~root/.bashrc:
alias kill='echo "Sorry, you'\''re too dumb for this"; false'
:-)
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2002-11-03 2:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 21:13 [PATCHSET] Mobile IPv6 for 2.5.45 Krishna Kumar
2002-11-03 2:23 ` Werner Almesberger [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-02 1:15 Krishna Kumar
2002-11-02 3:00 ` YOSHIFUJI Hideaki / 吉藤英明
2002-11-02 8:36 ` Pekka Savola
2002-11-02 8:23 ` Jeff Garzik
2002-11-02 0:32 Venkata Jagana
2002-11-01 6:51 Venkata Jagana
2002-11-01 10:37 ` David S. Miller
2002-11-01 2:19 Krishna Kumar
2002-11-01 2:17 ` David S. Miller
2002-11-01 2:36 ` YOSHIFUJI Hideaki / 吉藤英明
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=20021102232308.A4482@almesberger.net \
--to=wa@almesberger.net \
--cc=kumarkr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).