Re: s6 problems logging

From: Sean MacLennan <seanm_at_seanm.ca>
Date: Sun, 27 Jan 2019 11:47:51 -0500

On Sun, 27 Jan 2019 05:20:00 +0000
Colin Booth <colin_at_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
Received on Sun Jan 27 2019 - 16:47:51 UTC