info-cvs
[Top][All Lists]
Advanced

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

Re: cvshome.org (was Re: New email address)


From: Riley Williams
Subject: Re: cvshome.org (was Re: New email address)
Date: Wed, 31 Oct 2001 22:52:29 +0000 (GMT)

Hi Brian.

>> When I had a look for it on Sunday morning, I found the following
>> mappings (from memory):
>>
>>      cvs.cvshome.org         127.0.0.9
>>      www.cvshome.org         127.0.0.15

> That's totally bizarre, and I can't explain it.

That's what I thought, but the mappings were consistent over the 45
minutes or so that I was trying to work out what was going on, and were
there both from my own system (near Preston, Lancashire, England), from
a friend's system I have ssh access to in Cambridge, England, and from
another friend's system I have ssh access to in Aberdeen, Scotland, so
whatever it was wasn't localised to me...

>> I've just tried again, and see the following mapping at the moment:
>>
>>      cvs.cvshome.org         64.125.132.231  64.125.132.213

> Hmm, it should only be .231, and I'm not sure why you got .213.

I can now confirm that the .213 is no more, thankfully.

>> cvs [update aborted]: connect to cvs.cvshome.org(64.125.132.231):2401
>>      failed: connection refused

> We moved the box, but smtp & pserver didn't come up when it powered
> back on - not sure why, but it's on now.  Also, ftp to
> ftp.cvshome.org should work now as well.

I haven't tried ftp, but I'll describe the setup here...

 1. I am involved with a variety of CVS projects, and have them all
    stored under ~/CVS/Source/ here. Most of them, I'm using :ext:
    over ssh to access them, and have ssh-agent configured here so I
    don't need to type in the passwords every time.

 2. I have the following script run daily...

        #!/bin/bash

        source ~/bin/ssh-agent-autostart

        export NOW=`date +%Y-%m-%d`

        for DIR in * ; do
            if [ -d "$DIR" ]; then
                cd "$DIR"
                if [ -d CVS ]; then
                    FILE=../Logs/"${DIR}".${NOW}
                    echo -n Updating ${DIR} '=> '
                    cvs diff -u5 > "${FILE}.diff"
                    if [ ! -s "${FILE}.diff" ]; then
                        rm -f "${FILE}.diff"
                    fi
                    cvs update -d -P 2>&1 > "${FILE}.log"
                    if [ ! -s "${FILE}.log" ]; then
                        rm -f "${FILE}.log"
                    fi
                    echo Done.
                fi
                cd ..
            fi
        done

    ...which goes through everything that I have current CVS sources
    for, and updates them with whatever changes others have made in
    the meantime, logging any transactions to the relevant logfile.
    This keeps me synchronised with the various source trees daily,
    so I rarely have to worry about what others are doing, and I also
    get daily snapshots of the differences.

 3. When I'm ready to commit any changes, I do that manually.

This, for me at least, produces a system whereby I can develop what's
needed without worrying overmuch about what others are doing. It was
when I browsed through the logfiles that I noticed the problems with
cvshome.org and started investigating them.

Best wishes from Riley.




reply via email to

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