supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "Dewayne Geraghty" <dewayne.geraghty@heuristicsystems.com.au>,
	supervision@list.skarnet.org
Subject: Re: s6-log can create current with 640?
Date: Wed, 23 Oct 2019 23:58:58 +0000	[thread overview]
Message-ID: <emdb2737ee-616d-424d-8a41-8c813d7263f6@elzian> (raw)
In-Reply-To: <01b8c564-887f-16cf-405c-8bcfc52c02b1@heuristicsystems.com.au>

>My initial attempt
>
>#!/usr/local/bin/execlineb -P
>s6-setuidgid uucp
>redirfd -r 0 /services/ntp/fifo
>umask 037
>/usr/local/bin/s6-log -b n14 r7000 s100000 S3000000 !"/usr/bin/xz -7q"
>/var/log/ntpd

  Hi Dewayne,

  - Is there a reason why you're using a manually created fifo instead
of the built-in logging facility offered by s6-svscan? You could tell
ntpd to log to /dev/stdout, and have the logger in a ntpd/log service
directory, and your logs would automatically be available on your
logger's stdin.

  - About umask: that's very strange. Can you strace, or ktrace, or
whatever tool gives you a list of system calls, the script? It will
show exactly what's going on.

--
  Laurent



  reply	other threads:[~2019-10-23 23:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  2:27 Dewayne Geraghty
2019-10-23  4:53 ` Colin Booth
2019-10-23  5:39   ` Dewayne Geraghty
2019-10-23  7:15 ` Jonathan de Boyne Pollard
2019-10-23 23:03   ` Dewayne Geraghty
2019-10-23 23:58     ` Laurent Bercot [this message]
2019-10-25  8:20       ` Dewayne Geraghty
2019-10-25 17:06         ` Guillermo
2019-10-26  1:52           ` Dewayne Geraghty
2019-10-26  5:27             ` Laurent Bercot
2019-10-26  7:16               ` Dewayne Geraghty
2019-10-26 13:08                 ` Laurent Bercot
2019-10-29  7:28               ` Jonathan de Boyne Pollard
     [not found]               ` <a8fbd02e-0265-3d59-89d1-81048665693c@ntlworld.com>
2019-10-29  8:53                 ` Laurent Bercot

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=emdb2737ee-616d-424d-8a41-8c813d7263f6@elzian \
    --to=ska-supervision@skarnet.org \
    --cc=dewayne.geraghty@heuristicsystems.com.au \
    --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).