From: David Presotto <presotto@closedmind.org>
To: mirtchov@cpsc.ucalgary.ca, 9fans@cse.psu.edu
Subject: Re: [9fans] silent fossil crashes
Date: Tue, 2 Dec 2003 13:00:49 -0500 [thread overview]
Message-ID: <641560cf8de788503a8041d39b7aa670@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 83 bytes --]
Also (if you can) keep a 'con /srv/fscons' open somewhere
to see error messages...
[-- Attachment #2: Type: message/rfc822, Size: 2362 bytes --]
From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: [9fans] silent fossil crashes
Date: Tue, 2 Dec 2003 09:51:37 -0700
Message-ID: <c7e1e0281acf33d0d51f8cb7df42b5c1@plan9.ucalgary.ca>
it happened again -- fossil just stopped working without any sign of
error. no sysfatal, no crash, nothing. just stopped responding.
just when it died I had run a script that pulls from sources. the script does:
echo 'srv -AWP somethingsomething' >> /srv/fscons
at which point fossil decided to take a break.
i have a saved a serial console log of attempting to run ls, showing
that the machine isn't responding and then doing ^T^Tp and ^T^Tq
before the reboot. if anyone is interested.
^T^Tq didn't show any processes waiting in the queue, whish wasn't the
case with previous (nrdy>=1) crashes that were fixed a few weeks ago.
^T^Tk killed one of the fossil processes promptly.
hope that helps: andrey
next reply other threads:[~2003-12-02 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 18:00 David Presotto [this message]
2003-12-02 18:16 ` mirtchov
[not found] <2fd6338b88aeb4720c53adf22f3247f7@plan9.bell-labs.com>
2003-12-02 18:14 ` mirtchov
2003-12-02 18:16 ` Russ Cox
2003-12-02 20:29 ` jmk
-- strict thread matches above, loose matches on Subject: below --
2003-12-02 17:59 David Presotto
2003-12-02 16:51 mirtchov
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=641560cf8de788503a8041d39b7aa670@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
--cc=mirtchov@cpsc.ucalgary.ca \
/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).