From: carlsonj@workingcode.com
To: linux-ppp@vger.kernel.org
Subject: Re: Socket doesn't get EOF
Date: Wed, 17 Nov 2004 11:43:17 +0000 [thread overview]
Message-ID: <16795.14677.115819.798144@carlson.workingcode.com> (raw)
In-Reply-To: <41998875.2020305@blazemail.com>
K-sPecial writes:
> Thanks, that was very informative, it made sense and I much appreciate
> the prompt response. I have added a timeout on the socket and will get a
> glimpse of what happens next time pppd dies.
You can also have pppd clobber the application via the
/etc/ppp/ip-down script. I'd suggest that doing so is a mistake. If
the link comes back (it was just a short glitch), then the application
fails for no reason. If the network is designed with multiple paths,
then there's really no good way to know when (or if) to kill the
application.
Moreover, you'd have no way to know if some intermediate router
failed, and you'd likely want to have the application "notified" in
some way if that were to happen for the same reason that you want pppd
to kill the application. If you can't detect router failure in
practice, is there much additional value to detecting local interface
failure?
--
James Carlson <carlsonj@workingcode.com>
next prev parent reply other threads:[~2004-11-17 11:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 4:56 Socket doesn't get EOF K-sPecial
2004-11-16 20:49 ` carlsonj
2004-11-16 22:59 ` K-sPecial
2004-11-17 11:43 ` carlsonj [this message]
2004-11-17 23:41 ` K-sPecial
2004-11-18 12:04 ` James Carlson
2004-11-18 18:06 ` K-sPecial
2004-11-18 18:30 ` James Carlson
2004-11-18 18:54 ` K-sPecial
2004-11-18 19:29 ` James Carlson
2004-11-18 21:07 ` K-sPecial
2004-11-18 21:11 ` K-sPecial
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=16795.14677.115819.798144@carlson.workingcode.com \
--to=carlsonj@workingcode.com \
--cc=linux-ppp@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 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).