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>
Cc: Supervision <supervision@list.skarnet.org>
Subject: Re: s6-log can create current with 640?
Date: Sat, 26 Oct 2019 13:08:10 +0000	[thread overview]
Message-ID: <ema6c69ca4-29ca-400b-bbdb-2e49680e528a@elzian> (raw)
In-Reply-To: <cb4ac204-ffa7-21f0-cd8b-b9115084e967@heuristicsystems.com.au>

>A little bit more thought has resulted in a generic script which can
>implement any of the useless POSIX-required ``regular shell builtin''

Yeah, so it's another one of those functions that only make sense as
shell builtins but that are still also implemented as external commands.
Beats me why systems insist on having those commands, since they're 
never
invoked and are an utter waste of space.

The only solution to your predicament is to make sure that the location
of execline's umask binary in your PATH appears *before* the location
of the system umask binary. Normally that's the case, since the execline
utilities are in /usr/local/bin and the system utilities are in 
/usr/bin;
you should _always_ have /usr/local/bin before /usr/bin in your PATH,
because programs installed by the administrator should always override
programs installed by default by the distributor.

For some reason it's not the case in the execline script you're 
invoking;
you need to make sure your supervision tree is invoked with a proper 
PATH.

(Also, I'll have to write a posix-umask command in the same way as
posix-cd, but that's totally unrelated to your problem and wouldn't fix
your PATH issue.)

--
Laurent



  reply	other threads:[~2019-10-26 13:08 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
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 [this message]
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=ema6c69ca4-29ca-400b-bbdb-2e49680e528a@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).