From: "Rodrigo G. López" <rgl@antares-labs.eu>
To: 9front@9front.org
Subject: Re: [9front] listen: where does stderr go?
Date: Sun, 15 Mar 2020 16:03:33 +0000 [thread overview]
Message-ID: <C0BD7B66-5F79-46EA-978A-F3D414181623@antares-labs.eu> (raw)
In-Reply-To: <c6bd3295-8504-4d93-b2d0-378f1bd7580f@www.fastmail.com>
/sys/log/www.
read /rc/bin/service/tcp80
-rodri
On March 15, 2020 3:53:17 PM UTC, Ethan Gardener <eekee57@fastmail.fm> wrote:
>i'm setting up rc-httpd again. formerly, listen merged stderr & stdout
>into the output stream. this was useful for initial debugging. now,
>stderr is not present in the output stream. is it redirected to a file?
next prev parent reply other threads:[~2020-03-15 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 15:53 Ethan Gardener
2020-03-15 16:03 ` Rodrigo G. López [this message]
2020-03-15 16:10 ` [9front] " Ethan Gardener
2020-03-15 17:23 ` Ethan Gardener
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=C0BD7B66-5F79-46EA-978A-F3D414181623@antares-labs.eu \
--to=rgl@antares-labs.eu \
--cc=9front@9front.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).