Re: Project web site was gone for a while

[Dair G. <da...@re...>]

James W. Walker wrote:

>Friday night, I noticed that the web site at
><http://quesa.sourceforge.net/> was gone.  As in, no files there
>whatsoever.

Checking my spam folder shows that I got an error around that time as
well:

---------------------------------
cvs [export aborted]: end of file from server (consult above messages if
any)
rm: cannot remove `developer': Permission denied
rm: cannot remove `images': Permission denied
rm: cannot remove `index.html': Permission denied
rm: cannot remove `info': Permission denied
rm: cannot remove `other': Permission denied
rm: cannot remove `reference': Permission denied
mv: can't stat source /home/users/g/gr/grantd/tmp/quesa/Documentation/*
---------------------------------

It looks like something failed, although I'm not sure why - unless they
were doing something to the system while it was running.


>I would imagine that the cron job that keeps the site up=20
>to date would be doing a CVS update, so there shouldn't be any point
>at which it deletes everything.

Actually, it does - there isn't any standard support for doing an
automatic update, so I knocked something together:

---------------------------------
#!/bin/sh

# Check out the current source
cd ~/tmp
rm -fR quesa
cvs -d:pserver:anonymous@cvs1:/cvsroot/quesa -Q export -Dtomorrow
quesa/Documentation


# Replace the web site
cd /home/groups/q/qu/quesa/htdocs
rm -fR *
mv ~/tmp/quesa/Documentation/* .


# Clean out the temp directory
cd ~/tmp
rm -fR quesa
---------------------------------

The reason for removing the old directory first is that doing a cvs
update will fail if we move/rename any directories on the cvs server.

It'll handle renaming/moving files OK, but for directories rename
support is just non-existent in CVS.

I was expecting the above to always work, as even if Apache had some
files open and was serving them then we should still be able to remove
them.


>I re-uploaded the files and filed a SourceForge support request asking
>what happened.  But they don't work much on weekends, so there hasn't
>been any response yet.

What we could probably do is move the old directory somewhere else
first, check out the current state, and then try and delete the old
directory.

If that fails to delete for some reason then it's not such a big deal,
as the site will have been updated from cvs anyway (I guess we should do
the cvs checkout somewhere else, and check for an error before swapping
them over).

I've marked the sourceforge status stuff as non-spam now, so if it fails
regularly I should see it and can kick it off by hand.


-dair
___________________________________________________
mailto:dair+refnum.com       http://www.refnum.com/