* svlogd and /dev/stderr
@ 2008-06-03 0:35 Adam Megacz
0 siblings, 0 replies; only message in thread
From: Adam Megacz @ 2008-06-03 0:35 UTC (permalink / raw)
To: supervision
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-06-03 0:35 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-06-03 0:35 svlogd and /dev/stderr Adam Megacz
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).