From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] two questions: starting fgui? and emailing fossil vac scores?
Date: Mon, 5 Jan 2004 09:02:40 -0700 [thread overview]
Message-ID: <89168f6f7eed1854fbbb00e8ad2fb6a4@plan9.ucalgary.ca> (raw)
In-Reply-To: <72cc36dbcd7e42d020eb0ea671da328a@tombob.com>
> My second question is about something I've read on the list a couple
> of times. How do I set up automatic emailing of the vac scores
> generated by the archival snapshot in fossil? As in, a handy script I
> can cron or some such.
serve up a new console (fossil's srv -p command) and drain it with clog to a file somewhere in /sys/log (if you don't think you need to hide it from people). then a cron job to mail you the score every day is trivial.
in my case fossil's configuration file has (among other things):
srv -p fscmd
and cpurc for the file server has:
aux/clog /srv/fscmd /sys/log/fossil &
andrey
next prev parent reply other threads:[~2004-01-05 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 15:36 plan9
2004-01-05 16:02 ` mirtchov [this message]
2004-01-07 10:20 ` plan9
-- strict thread matches above, loose matches on Subject: below --
2003-12-19 12:18 plan9
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=89168f6f7eed1854fbbb00e8ad2fb6a4@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--cc=9fans@cse.psu.edu \
/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).