Re: s6 problems logging

From: Colin Booth <colin_at_heliocat.net>
Date: Sun, 27 Jan 2019 05:20:00 +0000

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
Received on Sun Jan 27 2019 - 05:20:00 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:44:19 UTC