Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Reply-To: <wpmccormick@covad.net>
From: "Bill McCormick" <wpmccormick@covad.net>
To: "Cygwin" <cygwin@cygwin.com>
Subject: RE: apache dies with pppoe
Date: Thu, 24 Jul 2003 08:07:07 -0500
Message-ID: <NDBBLLFMLFMANIDPNADCMEBLFCAA.wpmccormick@covad.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <3F1F81AC.C6A66057@wapme-systems.de>

> Carlo Florendo wrote:
> >
> > > I think this is a new one.
> > >
> > > I'm running Apache behind a nat'd f/w router attached to a
> dsl modem that
> > > dhcp's an ip from a pppoe connection.
> > >
> > > When the IP address changes, Apache must be restarted. At the
> moment I'm
> > > cron'ing a restart - but that's a kludge.
> > >
> > > Anybody have a similar setup with a better solution to keep
> Apache going?
> >
> > What does this have to do with cygwin?
>
> agreed. This is a more generic problem on how to bind to interfaces
> that do change it's IP nature.
>
> Stipe

Right, sorry ... I was a little vague on where I was going with this. Let me
try again.

Well, the way I see it based on what I I've read elsewhere, one solution
would be to have CYGwin detect that the WAN IP has changed. I'm not sure if
that's possible or not. I use DynDNS.org to get a dynamic DNS, if that
helps. I suppose I could write a little program, but I hate to re-invent the
wheel. So far, it seems not to be an Apache configuration issue, but I'm
still looking into that too.


Thanks,


Bill

Bill
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/