From: Sean MacLennan <seanm@seanm.ca>
To: Colin Booth <colin@heliocat.net>
Cc: supervision@list.skarnet.org
Subject: Re: s6 problems logging
Date: Sun, 27 Jan 2019 11:47:51 -0500 [thread overview]
Message-ID: <20190127114751.169d2a15@zonker.seanm.ca> (raw)
In-Reply-To: <20190127052000.4skktmkfzmit6ykl@cathexis.xen.prgmr.com>
On Sun, 27 Jan 2019 05:20:00 +0000
Colin Booth <colin@heliocat.net> wrote:
> Everything looks fine from over here. Does running doorknob with -fs
> from the terminal do what you expect?
Yup, I get a log message to the console when I send an email.
> Also, what does
> `s6-svstat PATH_TO_DOORKNOB_SVCDIR' and
> `s6-svstat PATH_TO_DOORKNOB_SVCDIR/log'
> tell you?
/service/doorknob# /command/s6-svstat .
up (pid 948) 47861 seconds
/service/doorknob# /command/s6-svstat log
up (pid 847) 75815 seconds
Log has been up longer because I restarted doorknob with an s6-svc
down/up. Not sure if this is kosher with logging. Is there a
recommended way to start/stop services that have logging?
> 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.
/service/doorknob# ls log
current event lock run state supervise
So it does have all the files/directories but current is empty even
though there should be some log entries.
I do use s6-log in one other service and it works. In the
service/s6-svscan-log I have:
#!/command/execlineb -P
cat ./fifo
And the same log/run as doorknob.
Cheers,
Sean
next prev parent reply other threads:[~2019-01-27 16:47 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
2019-01-27 16:47 ` Sean MacLennan [this message]
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=20190127114751.169d2a15@zonker.seanm.ca \
--to=seanm@seanm.ca \
--cc=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).