9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Robert Raschke <rtrlists@googlemail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] file server?
Date: Fri, 14 Aug 2009 09:45:39 +0100	[thread overview]
Message-ID: <6a3ae47e0908140145r2ccbdf54xe3ed1eeca598d9ea@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.00.0908140000060.8707@legolas.yyc.orthanc.ca>

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]

On Fri, Aug 14, 2009 at 7:14 AM, Lyndon Nerenberg <lyndon@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 fossil@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

[-- Attachment #2: Type: text/html, Size: 1601 bytes --]

  reply	other threads:[~2009-08-14  8:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14  0:30 Benjamin Huntsman
2009-08-14  0:55 ` andrey mirtchovski
2009-08-14  1:01   ` erik quanstrom
2009-08-14  1:23     ` John Floren
2009-08-14  2:00       ` erik quanstrom
2009-08-14  6:14       ` Lyndon Nerenberg
2009-08-14  8:45         ` Robert Raschke [this message]
2009-08-14 12:07           ` erik quanstrom
2009-08-14 12:44             ` Robert Raschke
2009-08-14 12:09         ` erik quanstrom
2009-08-16  2:12         ` Adrian Tritschler
2009-08-14  4:16     ` Lyndon Nerenberg
2009-08-14  1:09   ` Federico G. Benavento
2009-08-14  1:15 ` blstuart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a3ae47e0908140145r2ccbdf54xe3ed1eeca598d9ea@mail.gmail.com \
    --to=rtrlists@googlemail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).