Well, perhaps, but since the question was about runit then I thought this
would be more useful information than suggesting changing software
entirely. Actually, I rather like this approach myself. The configuration
is still all in one place, it's more flexible, and fully optional. Runit
even takes care of resolving the symlinks and creating folders for you.
--Mike
On Sep 17, 2013 6:46 AM, "Uffe Jakobsen" <uffe_at_uffe.org> wrote:
>
>
> On 2013-09-17 14:20, Mike Buland wrote:
>
>> Actually, runit can handle this just fine as well, I store all of my
>> supervise folders in the /run tree using symlinks, and all logs in the
>> /var/log directory, also using symlinks. Runit is very symlink friendly
>> :)
>>
>>
> that is the exact setup that I want to avoid - I don't like such tweaks -
> and daemontools-encore solves this for me out of the box
>
> /Uffe :-)
>
>
>>
>> On Tue, Sep 17, 2013 at 5:25 AM, Uffe Jakobsen <uffe_at_uffe.org> wrote:
>>
>>
>>> On 2013-09-17 06:23, Laurent Bercot wrote:
>>>
>>>
>>>> Hi, folks. Does anyone see any problem with storing full service
>>>>
>>>>> directories, including logs and supervise fifos, on NFS-mounted
>>>>> filesystems? It appears to work fine in my trials, but I'm curious if
>>>>> anyone else has any experience with this, and knows if there are any
>>>>> gotchas I might face down the road. Thanks.
>>>>>
>>>>>
>>>> Hi Jamie,
>>>>
>>>> Don't do it.
>>>> The point of NFS is to share a part of the filesystem across several
>>>> computers. A supervised service is local to a machine; service
>>>> directories store local information. Things such as service PID and
>>>> lock file cannot be shared. (Even if NFS locking works, you don't want
>>>> to prevent a service from starting up on a machine because the same
>>>> service is already up on another.)
>>>>
>>>> Keep local information on local filesystems.
>>>>
>>>>
>>>> FYI
>>>
>>> One solution could be daemontools-encore by Bruce Guenter
>>>
>>> daemontools-encode (supervise) supports storing the status files in an
>>> alternate directory specified by $SUPERVISEDIR.
>>>
>>> See: Environment
>>> http://untroubled.org/****daemontools-encore/supervise.****8.html#toc3<http://untroubled.org/**daemontools-encore/supervise.**8.html#toc3>
>>> <http://**untroubled.org/daemontools-**encore/supervise.8.html#toc3<http://untroubled.org/daemontools-encore/supervise.8.html#toc3>
>>> >
>>>
>>> This feature was requested by me (and others) that use daemontools on
>>> embedded systems that had most of its filesystems mounted readonly.
>>>
>>> Hence it is possible to split service definitions and its dynamic
>>> runtime informations - quite handy
>>>
>>> /Uffe
>>>
>>>
>
>
>
Received on Tue Sep 17 2013 - 14:36:08 UTC