From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] multiple pings cause panic
Date: Sun, 18 Apr 2010 22:53:40 -0400 [thread overview]
Message-ID: <e85a0697265f18ad4f028dbc7c4df531@kw.quanstro.net> (raw)
In-Reply-To: <7dfb5c700d4fe23dedbb15cba8dfd966@gmx.de>
On Sun Apr 18 21:21:10 EDT 2010, cinap_lenrek@gmx.de wrote:
> if one wants to retry connecting he can.
if you're primarly functioning as a server, that might be true,
but not helpful. you may just appear down. it's just no fun
to get the call "i can't (read my mail|cpu in|...)" at 2am. i'd
much rather the dumb machine panic and reboot automaticly.
but i'm biased because my fileservers doesn't care, and you can't
connect to them remotely.
> not being able to make a
> network connection is a very common case so i guess it would be ok to
> simply let it fail on this point instead of hanging and waiting.
>
> rebooting sounds like a little bit too drastic for me. expecially if it
> is about icmp sockets. devip just has too less context to make a good
> decision.
>
> the comment above the panic call also hinted that it was ment as some
> kind of a bet or a debugging leftover so it felt save to remove it :)
panicing is not right. all i'm saying is that printing might not really
help either. i don't think either of us have the testing resources to
be confident that your patch is going to be a significant win. it
looks fine, but i don't want to find out at 2am it's not really.
after all, i haven't yet had a panic due to this and i've got some
(unintentionally) tough customers. they've got deadlines, too.
- erik
prev parent reply other threads:[~2010-04-19 2:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 19:36 James Chapman
2010-04-18 20:32 ` erik quanstrom
2010-04-18 20:54 ` James Chapman
2010-04-18 21:19 ` erik quanstrom
2010-04-18 20:39 ` geoff
2010-04-18 23:52 ` erik quanstrom
2010-04-19 0:23 ` cinap_lenrek
2010-04-19 0:27 ` erik quanstrom
2010-04-19 1:19 ` cinap_lenrek
2010-04-19 1:27 ` andrey mirtchovski
2010-04-19 2:53 ` erik quanstrom [this message]
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=e85a0697265f18ad4f028dbc7c4df531@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).