2015-09-24 22:35 GMT-03:00 Laurent Bercot:
>
> But I guess it doesn't cost much to add support for -wr/-wR, if
> you want it.
No need, I was just curious :)
Thank you,
G.
On 25/09/2015 03:18, Guillermo wrote:
Reading the documentation, I couldn't tell the difference between
these and the -wu and -wU options. Looking at the code, -r seems to
mean "wait for a D event, and then for an u event", and -R seems to
mean "wait for a D event, and then for an U event". Is th
On Thu, Sep 24, 2015 at 02:09:56PM +0200, Laurent Bercot wrote:
> On 24/09/2015 13:56, Patrick Mahoney wrote:
> >Hi, the website says it requires "s6 version 2.2.1.0 or later", but I'm
> >getting
> >a compile error:
>
> You probably got a version where package/info said 2.2.1.0 but the
> tag was
Hi,
2015-09-23 17:10 GMT-03:00 Laurent Bercot:
>
> * s6-2.2.1.0
>
>
> [...]
> New -wr and -wR options to s6-svc, s6-svlisten1 and s6-svlisten.
Reading the documentation, I couldn't tell the difference between
these and the -wu and -wU options. Looking at the code, -r seems to
mea
On 9/24/2015 12:29 PM, Laurent Bercot wrote:
On 24/09/2015 18:45, Avery Payne wrote:
This is probably the only real problem in the arrangement I'm using
then. The entire premise is "the support scripts live where the
definitions live and are called with relative pathing, allowing the
definiti
On 24/09/2015 18:45, Avery Payne wrote:
This is probably the only real problem in the arrangement I'm using
then. The entire premise is "the support scripts live where the
definitions live and are called with relative pathing, allowing the
definitions to be located anywhere".
My point of view
On 9/24/2015 2:47 AM, Laurent Bercot wrote:
On 24/09/2015 04:54, Avery Payne wrote:
1. Copy the entire contents of the svcdef/ directory into the s6
source definition directory, including dot file support directories.
There is no room in the source definition directory for a support
directo
On Thu, Sep 24, 2015 at 2:23 AM, Laurent Bercot wrote:
> On 24/09/2015 02:55, Colin Booth wrote:
>> rc scripts are easy peasy: figure out dependency order, write
>> oneshots. The only one that was an issue is the udev script, and I
>> solved that by running udev as a oneshot, then running udev sto
On Thu, Sep 24, 2015 at 02:09:56PM +0200, Laurent Bercot wrote:
> On 24/09/2015 13:56, Patrick Mahoney wrote:
>
> >I was able to get a little farther using the master branch of s6 @ 1g8gr3z
>
> Just a little? Didn't you get everything compiled properly?
Not quite, stuck on
make: *** No rule
On 24/09/2015 13:56, Patrick Mahoney wrote:
Hi, the website says it requires "s6 version 2.2.1.0 or later", but I'm getting
a compile error:
You probably got a version where package/info said 2.2.1.0 but the
tag wasn't there yet. As long as "git tag" doesn't list "v2.2.1.0"
then it's not 2.2.1
On Wed, Sep 23, 2015 at 10:59:37PM +0200, Laurent Bercot wrote:
>
> s6-rc-0.0.1.0 is out.
Hi, the website says it requires "s6 version 2.2.1.0 or later", but I'm getting
a compile error:
src/libs6rc/s6rc_servicedir_manage.c: In function 's6rc_servicedir_manage':
src/libs6rc/s6rc_service
On 24/09/2015 04:54, Avery Payne wrote:
1. Copy the entire contents of the svcdef/ directory into the s6
source definition directory, including dot file support directories.
There is no room in the source definition directory for a support
directory as svcdef/ ; I mean, you can put it anywhere
On 24/09/2015 02:55, Colin Booth wrote:
There might be a chance that s6-rc-compile derefrences symlinks into
real files, or just bulk copies those files without massaging them. If
either is the case it should be safe to just put those into place with
the target pointing in the right place (the re
13 matches
Mail list logo
