From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] pprint and exportfs (and others)
Date: Wed, 17 Apr 2013 22:20:01 -0400 [thread overview]
Message-ID: <d21bfe7c202aa8a97941afbbb76ba2ee@kw.quanstro.net> (raw)
In-Reply-To: <6347546d290fb03ae4970d19b685a5d9@rei2.9hal>
> having errors from listeneres appear on the cpu server console
> (or a logfile?) instead in the middle of some unknown protocol
> stream makes sense as a default for aux/listen.
a logfile would be better. i have a system that gets
attacked occasionally, and spamming the console
would only make matters worse. however, having
the service/whatever script redirect to a log file
might be an improvement. listen perhaps could
open /dev/null on stderr and leave it up to the script.
- erik
next prev parent reply other threads:[~2013-04-18 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 16:52 Charles Forsyth
2013-04-17 17:35 ` lucio
2013-04-17 17:43 ` erik quanstrom
2013-04-17 17:52 ` lucio
2013-04-17 21:07 ` Charles Forsyth
2013-04-17 21:55 ` cinap_lenrek
2013-04-18 2:20 ` erik quanstrom [this message]
2013-04-20 19:15 ` cinap_lenrek
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=d21bfe7c202aa8a97941afbbb76ba2ee@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).