savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers] Re: Web page update through CVS


From: loic
Subject: Re: [Savannah-hackers] Re: Web page update through CVS
Date: Fri, 25 May 2001 22:57:14 +0200

Paul Visscher writes:
 > Daniel Bump address@hidden said:
 > > I've been maintaining the web pages of GNU Go through the
 > > cvs at subversions.gnu.org.
 > > 
 > > Last night I made a revision to 
 > > http://www.gnu.org/software/gnugo/devel.html
 > > and successfully checked in my changes to the
 > > repository at address@hidden:/webcvs/.
 > > 
 > > In the past when I've done this the web page 
 > > gets updated. This time it hasn't. 
 > > 
 > > Is something broke?
 > 
 > bkuhn and I noticed this today, too. I believe something was broken, but
 > it appears to be working now. savannah-hackers: do you know what the
 > status of this is?


        Hi,

        Around 9pm yesterday night the former ns1.varesearch.com known
under the IP 209.81.8.8 ceased to work. Since the reverse of
209.81.8.8 is still ns1.varesearch.com I was a bit confused.  The new
ns1.varesearch.com is now 198.186.202.135.

        This had an interesting effect on gnudist.gnu.org and
subversions.gnu.org. Since the resolv.conf file of gnudist.gnu.org
only listed 209.81.8.8 it became unable to do minor things, such
as keeping the www.gnu.org web site in sync with the CVS tree on
subversions.gnu.org. 

        The effect on subversions.gnu.org was less dramatic because
209.81.8.8 was only the first of three alternatives. Still it introduced
annoying delays when trying to login using ssh, for instance. 

        I fixed the gnudist.gnu.org resolv.conf with the following:

search gnu.org ai.mit.edu mit.edu varesearch.com
nameserver 127.0.0.1
nameserver 199.232.76.162
nameserver 195.68.21.198

        and just removed the offending line from the resolv.conf of
subversions.gnu.org. It might be worth checking the other machines for
the infamous 209.81.8.8.

        This might not be the ideal setup but I've no clue what the
policy should be.

        After this I manually re-synced the www.gnu.org web site to
ensure that it is up to date with the CVS tree. Everything is fine
now. I'm not going to apologize for VA Linux. Unless they sent us a
warning but I sincerly doubt they did.

        Take care,

-- 
Loic   Dachary         http://www.dachary.org/  address@hidden
24 av Secretan         http://www.senga.org/      address@hidden
75019    Paris         Tel: 33 1 42 45 09 16        address@hidden
        GPG Public Key: http://www.dachary.org/loic/gpg.txt



reply via email to

[Prev in Thread] Current Thread [Next in Thread]