From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <88a9af7391485cdebb64b1945221bc6c@mail.gmx.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme crash recovery
From: "Sascha Retzki" <sretzki@gmx.de>
Date: Mon,  7 Aug 2006 20:15:38 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 98c8326a-ead1-11e9-9d60-3106f5b1d025

> acme, like sam, keeps a log of changes in /tmp/*acme.  I believe that
> such a file contains enough to reconstruct acme's state when (or
> shortly before) it crashed, but I don't know of an automated means of
> doing so.

Yes, that is what fgb told me to look for, too. Thanks.

Acme possibly never got a kill-note, tho - I rebooted via Ctrl+Alt+Del. Other possibilities include that I fire up acme on startup, so maybe acme cleans up /tmp ;)

No matter which one is right, there wasn't a /tmp/$number.$useracme-file containing my sources.


I tried a grep over things like /tmp, /sys/, /acme/, /usr, etc for function-names, so I am pretty sure the source-file is gone. Next version probably contains less design flaws, I am back up in the mood to (re)write it. 


> it won't do dumps if there isn't a venti to archive them, but
> try 9fs snap and see if there is anything in /n/snap.
> you might be lucky.

tried 9fs snap, too. Did not work, too.



Thanks for your time, Sascha