On 08/01/15 17:53, Avery Payne wrote:
The use of hidden directories was done for administrative and aesthetic
reasons. The rationale was that the various templates and scripts and
utilities shouldn't be mixed in while looking at a display of the various
definitions.
Why shouldn't they be
Here's an ugly hack that allows you do that using envdir:
set -a
eval $({ env; envdir ../.env env; } | grep -vF -e _= -e SHLVL= | sort | uniq -u)
set +a
Ugh, in the morning (almost) light it's even uglier than I thought,
because it won't work for values you *change* either, which could
be
I'll be following this intently as I have a project I'm working on that will
use s6 heavily even discretely.
Sent from my Windows Phone
From: Avery Paynemailto:avery.p.pa...@gmail.com
Sent: 1/7/2015 11:58 PM
To:
On Wed, 7 Jan 2015 14:25:28 -0800
Avery Payne avery.p.pa...@gmail.com wrote:
On Wed, Jan 7, 2015 at 7:23 AM, Steve Litt sl...@troubleshooters.com
wrote:
I'm pretty sure this conforms to James' preference (and mine
probably) that it be done in the config and not in the init program.
The use of hidden directories was done for administrative and aesthetic
reasons. The rationale was that the various templates and scripts and
utilities shouldn't be mixed in while looking at a display of the various
definitions. The other rationale was that the entire set of definitions
could be
On Thu, Jan 8, 2015 at 9:23 AM, Steve Litt sl...@troubleshooters.com
wrote:
I'm having trouble understanding exactly what you're saying. You mean
the executable being daemonized fails, by itself, because a service it
needs isn't there, right? You *don't* mean that the init itself fails,
