On Tue, Apr 28, 2015 at 8:38 AM, Avery Payne avery.p.pa...@gmail.com wrote:
The steps described are explicit and hard-coded into a service's ./run
script. This design works just OK and ensures complicated start-up
sequences can be carried out, but it does not allow easy replacement of
child
On Tue, Apr 28, 2015 at 9:08 AM, Avery Payne avery.p.pa...@gmail.com wrote:
On 4/28/2015 6:56 AM, bougyman wrote:
https://github.com/voidlinux/void-runit
The list of directories in /services only shows entries for getties, are all
of the other definitions inside of their respective packages?
Dang it. Hit the send button.
It will be a bit, I'll follow up with the completed email. Sorry for
the half-baked posting.
On Tue, Apr 28, 2015 at 12:31 PM, Steve Litt sl...@troubleshooters.com wrote:
Good! I was about to ask the definitions of parent and child, but the
preceding makes it clear.
Well at least we're talking the same language now, though reversing
parent/child is
disconcerting to my OCD.
Here's
On 4/28/2015 10:50 AM, bougyman wrote:
Well at least we're talking the same language now, though reversing
parent/child is disconcerting to my OCD.
Sorry if the terminology is reversed.
Here's the current version of run.sh, with dependency support baked
in:
On 4/28/2015 11:34 AM, Laurent Bercot wrote:
If a lot of people would like to participate but don't want to
subscribe to the skaware mailing-list, I'll move the thread here.
Good point, I'm going to stop discussion here and go over there, where
the discussion belongs.
On 4/28/2015 10:31 AM, Steve Litt wrote:
Good! I was about to ask the definitions of parent and child, but the
preceding makes it clear.
I'm taking it from the viewpoint that says the service that the user
wishes to start is the parent of all other service dependencies that
must start.
On 28/04/2015 20:49, Avery Payne wrote:
Good point, I'm going to stop discussion here and go over there, where the
discussion belongs.
That's not what I meant :)
Keep your thread here, it interests people who are not subscribed
to skaware, and it will be simpler. But please come over there
Quite a lot of clock-cycles are being devoted to the discussion of
dependencies among services.
I would like to suggest that not all dependencies are created equal.
That is, some (if not most) dependencies are really of no practical
consequence -- and we don't need to worry about them in terms of
