From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] silent fossil crashes
Date: Tue, 2 Dec 2003 13:16:53 -0500 [thread overview]
Message-ID: <E1ARF4w-000PnY-18@t40.swtch.com> (raw)
In-Reply-To: Your message of "Tue, 02 Dec 2003 11:14:17 MST." <bb5b796f75771b1f9ce8549b936f0940@plan9.ucalgary.ca>
> > How many tcp connections are open to that fossil (if any)?
>
> not too many.. i had two clients connected to it. the total number
> of fossil processes at the time of crash were 23, so about 15-20 tcp
> connections.
i'd be interested to see the ^t^tp list.
also the output of "msg" on your current console.
next prev parent reply other threads:[~2003-12-02 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2fd6338b88aeb4720c53adf22f3247f7@plan9.bell-labs.com>
2003-12-02 18:14 ` mirtchov
2003-12-02 18:16 ` Russ Cox [this message]
2003-12-02 20:29 ` jmk
2003-12-02 18:00 David Presotto
2003-12-02 18:16 ` mirtchov
-- 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=E1ARF4w-000PnY-18@t40.swtch.com \
--to=rsc@swtch.com \
--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).