From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] remote access to fossil console
Date: Tue, 2 Dec 2003 14:06:45 -0700 [thread overview]
Message-ID: <a93154c8c7dc33966cd13aeeaf7d6ceb@plan9.ucalgary.ca> (raw)
In-Reply-To: <200312022051.hB2KpSe23133@zamenhof.cs.utwente.nl>
> I haven't kept up reading 9fans over the last months -- are there
> new ideas people are employing to capture (at least) the fingerprints
> in a 'safe' place (and possibly other (error) messages too?)
Nemo prints them on paper which is a very good idea IMHO. I use the
logging jmk suggested and have a console srv-ed that drains to
/sys/log/fossil:
aux/clog /srv/fslog /sys/log/fossil &
every morning the latest vac score is mailed to and stored on a
university-administered machine, so I don't need to worry about
backing the scores up.
andrey
next prev parent reply other threads:[~2003-12-02 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 19:18 jmk
2003-12-02 20:51 ` Axel Belinfante
2003-12-02 21:06 ` mirtchov [this message]
2003-12-02 21:22 ` Axel Belinfante
2003-12-02 20:55 ` Russ Cox
2003-12-03 1:47 ` Dan Cross
2003-12-02 23:27 ` Geoff Collyer
2003-12-03 2:32 ` boyd, rounin
2003-12-02 21:30 David Presotto
2003-12-03 2:37 ` boyd, rounin
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=a93154c8c7dc33966cd13aeeaf7d6ceb@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).