9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Sascha Retzki" <sretzki@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme crash recovery
Date: Mon,  7 Aug 2006 20:15:38 +0200	[thread overview]
Message-ID: <88a9af7391485cdebb64b1945221bc6c@mail.gmx.net> (raw)

> 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



             reply	other threads:[~2006-08-07 18:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 18:15 Sascha Retzki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-06 15:59 Sascha Retzki
2006-08-07  8:57 ` Robert Raschke
2006-08-07 10:08 ` erik quanstrom
2006-08-07  2:28   ` geoff
2006-08-15 18:20     ` rog
2006-08-15 18:36       ` Paul Lalonde
2006-08-07  6:31   ` Charles Forsyth

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=88a9af7391485cdebb64b1945221bc6c@mail.gmx.net \
    --to=sretzki@gmx.de \
    --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).