From: Jeremy Cowgar <jcowgar@advancedpricing.com>
To: help-gnats@gnu.org
Subject: RE: Gnatsweb: Unparseable reply from gnatsd
Date: Tue, 15 Mar 2005 17:54:00 -0000 [thread overview]
Message-ID: <20050315122905.wc8goncrwzk0ggkg@horde.advancedpricing.com> (raw)
In-Reply-To: <20050315170600.3290EE90F1@mail.advancedpricing.com>
Quoting Stuart Stevens <stuart_stevens@sierralogic.com>:
> One reason that the reply is unparseable if it is blank is if the server
> dies unexpectedly. I have seen this happen with 4.0.
Any ideas on how to tell why the server died?
Jeremy Cowgar
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
next parent reply other threads:[~2005-03-15 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050315170600.3290EE90F1@mail.advancedpricing.com>
2005-03-15 17:54 ` Jeremy Cowgar [this message]
2005-03-15 18:11 ` Chad Walstrom
2005-03-16 6:43 ` Chad Walstrom
2005-03-14 19:41 Jeremy Cowgar
2005-03-14 20:57 ` Chad Walstrom
2005-03-15 3:38 ` Jeremy Cowgar
2005-03-15 17:36 ` Stuart Stevens
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=20050315122905.wc8goncrwzk0ggkg@horde.advancedpricing.com \
--to=jcowgar@advancedpricing.com \
--cc=help-gnats@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).