linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: K-sPecial <spam@blazemail.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Socket doesn't get EOF
Date: Thu, 18 Nov 2004 21:07:05 +0000	[thread overview]
Message-ID: <419D0EF9.7080903@blazemail.com> (raw)
In-Reply-To: <41998875.2020305@blazemail.com>

> Sure ... but why does it hurt to change the IP address when "the link"
> is down?
> 

Because I don't want the script to go into the loop of checking if it's 
back up again if it wasn't down in the first place. I guess it wouldn't 
hurt because all that would happen is it would update the hostname with 
the ip it's already at (the "old" ip) and things would be gravy. But 
remember at the time I said it waits 10 minutes or whatever is specified 
before updating if it thinks it's down (connect() doesn't succeed on the 
port), what if in these 10 minutes your Internet came available, then 
unless it checks if it's online, the ip would be changed to the ip to 
change to when the service on the port can't be reached because of that 
services computer.

> That's precisely the point.
> The thing that makes a host unreachable might be zero, one, or many
> hops away.  Worrying about the local interface(s) or about one
> particular local router is just useless.

Yay! We *do* agree.

> Anway, as I've said multiple times now, you can determine precisely
> whether PPP is up or down (and get notifications when it goes up and
> down) by using any of SIOCGIFCONF, PF_ROUTE, or /etc/ppp/ip-{up,down}.
> You do not need to have the socket connection aborted with an error in
> order to find out this information.

Yes, for ppp that is great, thanks, thanks alot.

--K-sPecial

[ http://xzziroz.freeshell.org
   irc://xzziroz.dtdns.net       ]





  parent reply	other threads:[~2004-11-18 21:07 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
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 [this message]
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=419D0EF9.7080903@blazemail.com \
    --to=spam@blazemail.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).