savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] Re: gcc at subversions


From: Loic Dachary
Subject: [Savannah-hackers] Re: gcc at subversions
Date: Sun, 25 Nov 2001 16:17:05 +0100

Jason Molenda writes:
 > The idea is that subversions.gnu.org would wget the pre-determined
 > URL every, say, fifteen minutes, and would rsync over the files
 > that had been modified in that time interval.

        That would speed up the process, definitely. There is a risk,
though, since that specific hack will have to work reliably now and
for the time being. As soon as there is a two line shell script there
is maintenance, people forgeting it was there ... ;-)

 > Less often (e.g. once a day) they'd do a full-blown rsync to pick
 > up any CVS tags that had been added, for instance.  (cvs tag won't
 > go through log_accum)
 > 
 > It's just an idea I've been kicking around for a while, not something
 > I'm committing to doing right away.  But it seems like it could be
 > useful for this sort of thing.

        I agree.

 > > > Of course the risk is that we mirror a locked file and that during an
 > > > hour the corresponding file is not available. I'm not sure what would
 > > > be the easiest way to avoid this problem.
 > 
 > This doesn't cause troubles in practice.  rsync builds the file
 > list on the server, then does the same on the client, then sends
 > any modified files.  By then, the lock files have moved on the
 > server side.  
 > 
 > You can add the lock files to rsync's exclude regexps (and this is
 > what I've done for the CVS repository on gcc.gnu.org), but rsync
 > will unhelpfully give you an "I/O error" when one of these files
 > disappears between steps, even though you've declared you're not
 > interested in them.
 > 
 > Anyway, on the off chance that a lock file remained through all the
 > steps, rsync should exclude it given the config on this system.

        This is good. Since we are rsync'ing from gcc.gnu.org, we are
out of trouble because the server side already excludes the lock files
(just re-stating what you said to make sure there is 0% chance of
misunderstanding). Here is the line we use:
        
        rsync --archive --delete --checksum --compress 
rsync://sourceware.cygnus.com/gcc-cvs /home/rsync/gcc

        sourceware.cygnus.com == gcc.gnu.org therefore I guess we are talking
of the same rsync configuration.

        Cheers,

-- 
Loic   Dachary         http://www.dachary.org/  address@hidden
24 av Secretan         http://www.senga.org/      address@hidden
75019    Paris         T: 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]