From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Can I redirect logs to file, instead of using s command in sup console
Date: Sat, 03 Nov 2007 15:25:36 -0700 [thread overview]
Message-ID: <1194128631-sup-6070@south> (raw)
In-Reply-To: <472C4FD9.5060707@gslab.com>
Excerpts from Manish Sapariya's message of Sat Nov 03 03:39:21 -0700 2007:
> I want to see at the log files when sup crashes. I could not find any
> command line option and brief grepping in the sources did not gave any
> clue.
There's no way to do this currently. Typically the log doesn't actually
contain that much useful stuff for diagnosing a crash; the exception is
more information (written out to sup-exeption-log.txt currently).
Wouldn't be too hard to do this by modified Logger#log.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-11-03 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 10:39 Manish Sapariya
2007-11-03 22:25 ` William Morgan [this message]
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=1194128631-sup-6070@south \
--to=wmorgan-sup@masanjin.net \
/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