From: Adam Megacz <adam@megacz.com>
To: supervision@list.skarnet.org
Subject: svlogd and /dev/stderr
Date: Mon, 02 Jun 2008 17:35:10 -0700 [thread overview]
Message-ID: <xuu27id7we2p.fsf@nowhere.com> (raw)
Some packages provide an option for sending their logs to a file or to
syslog, but no option to send them to stderr or stdout. One such
package is atftpd. Most of these packages recommend that you simply
specify /dev/stderr (or /proc/self/fd/2) as a "log file" to get the
same effect.
Unfortunately, if the stderr file descriptor is an IPC pipe rather
than an actual file, the /proc/self/fd/2 symlink will be a link to
something like "pipe:[4018]" -- attempts to open() it will fail.
Has anybody else run into this problem? It isn't really a problem
with runit/svlogd, but it seems to mostly affect people who use
svlogd.
- a
reply other threads:[~2008-06-03 0:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=xuu27id7we2p.fsf@nowhere.com \
--to=adam@megacz.com \
--cc=supervision@list.skarnet.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 NNTP newsgroup(s).