On Fri, Aug 14, 2009 at 7:14 AM, Lyndon Nerenberg <lyn...@orthanc.ca> wrote:
> This is what we do at Sandia. We have one machine which serves
>> cpu/auth/file, but the actual Venti disks are in a Coraid connected
>> via GigE. The fossil disk is in the server, but if it dies we can just
>> build a new one.
>>
>
> Which reminds me of an often overlooked but important point:
>
> Save your fossil vac scores on another machine!
>
I have a nightly cron job that sends the latest output of the fossil console
as an email.
In cpurc of the fileserver I setup a
aux/clog /srv/fscmd /sys/log/fossil &
and my nightly batch just does this:
who = (myself fos...@some.other.place)
today = `{date}
tail -20 /sys/log/fossil |mail -s 'Fossil output of ' ^ $"today $who
The last 20 lines is probably overkill, but who cares.
The venti archive starts at 2AM, and my cron job is at 4AM. So far, I've not
yet had an archive take longer than 2 hours. But that's partly due to
triggering one explicitly after a pull that's just replaced all my
executables ;-)
Robby
