From: Colin Booth <colin@heliocat.net>
To: supervision@list.skarnet.org
Subject: Re: s6 problems logging
Date: Sun, 27 Jan 2019 05:20:00 +0000 [thread overview]
Message-ID: <20190127052000.4skktmkfzmit6ykl@cathexis.xen.prgmr.com> (raw)
In-Reply-To: <20190126221517.70ea00b8@zonker.seanm.ca>
On Sat, Jan 26, 2019 at 10:15:17PM -0500, Sean MacLennan wrote:
> I have a service called doorknob that I want to log the output of. Here
> is the run file:
>
> #!/command/execlineb -P
> /usr/sbin/doorknob -fs
>
> The -f keeps doorknob in the foreground and the -s sends all messages
> to stdout.
>
> The log/run file is:
>
> #!/command/execlineb -P
> s6-log -b n20 s1000000 t .
>
> My understanding is that the stdout should go to s6-log and be put in
> log/current. But nothing seems to be logged.
>
> Cheers,
> Sean
>
> https://github.com/smaclennan/doorknob
Everything looks fine from over here. Does running doorknob with -fs
from the terminal do what you expect? Also, what does
`s6-svstat PATH_TO_DOORKNOB_SVCDIR' and
`s6-svstat PATH_TO_DOORKNOB_SVCDIR/log'
tell you? Also, does the target dir for s6-log have the files "current"
(apparently not), "lock", and "state"? Those final two files are created
by s6-log automatically and should at least indicate that it's starting
up fine.
Cheers!
-Colin
--
Colin Booth
next prev parent reply other threads:[~2019-01-27 5:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-27 3:15 Sean MacLennan
2019-01-27 5:20 ` Colin Booth [this message]
2019-01-27 16:47 ` Sean MacLennan
2019-01-27 17:56 ` Laurent Bercot
2019-01-27 18:13 ` Colin Booth
2019-01-27 18:56 ` Sean MacLennan
2019-01-27 19:27 ` Roger Pate
2019-01-28 11:00 ` Peter Pentchev
2019-02-01 9:22 ` Jonathan de Boyne Pollard
2019-01-27 19:35 ` Guillermo
2019-01-27 14:39 ` smaclennan/doorknob Jonathan de Boyne Pollard
2019-02-02 18:32 ` smaclennan/doorknob Sean MacLennan
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=20190127052000.4skktmkfzmit6ykl@cathexis.xen.prgmr.com \
--to=colin@heliocat.net \
--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).