Re: service directory on NFS-mounted filesystem

From: Uffe Jakobsen <>
Date: Tue, 17 Sep 2013 13:25:44 +0200

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.


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

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

Received on Tue Sep 17 2013 - 11:25:44 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:44:18 UTC