From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200312022051.hB2KpSe23133@zamenhof.cs.utwente.nl> To: 9fans@cse.psu.edu Subject: Re: [9fans] remote access to fossil console In-reply-to: Your message of "Tue, 02 Dec 2003 14:18:33 -0500." References: From: Axel Belinfante MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <23129.1070398288.1@zamenhof.cs.utwente.nl> Date: Tue, 2 Dec 2003 21:51:28 +0100 Topicbox-Message-UUID: 9aef1798-eacc-11e9-9e20-41e7f4b1d025 I think I did something like that on my fossil file server I had running a while ago (after disk problems and a full fossil it is in a 'under reconstruction' state for many months now). I used the clog program to log the fossil console output; this worked nicely, until the fossil filled up... then every write to the fossil also produced an error message via the fossil console that via clog tried to be logged to the already overfull fossile ad finitum (nauseum...) I'm wondering whether it would make sense to keep a kfs (or 9fat?) partition for logging purposes -- at least to capture/save the fossil/venti fingerprints. 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?) Axel. > Here's something I did last week to get remote access to the fossil > console using consolefs to our server called 'ehime':