On May 15, 2008, at 12:10 PM, Charles Duffy wrote:

> George Georgalis wrote:
>> On Tue 13 May 2008 at 10:48:59 AM +0000, Gerrit Pape wrote:
>>> Robin Bowes <robin-lists <at> robinbowes.com> writes:
>>>> Gerrit Pape wrote:
>>>>> When installing runit on a system that should comply with the  
>>>>> Filesystem
>>>>> Hierarchy Standard (FHS), neither /service/ nor /var/service/  
>>>>> should be
>>>>> chosen, but /etc/service/.  It is recommended to create a  
>>>>> compatibility
>>>>> symlink /service pointing to /etc/service in this case.
>>>> Is this for the actual service configurations, or the directory  
>>>> monitored by runsvdir-start ?
>>> The latter.
>> Why not /etc/service as a default for all systems?
>> (as I speculate it's related to /etc/opt : Configuration files for / 
>> opt)
>
> I've built netbooting/embedded systems where /etc was mounted read- 
> only. Putting the run, check, supervise and finish scripts there  
> makes sense -- but it would be nice if the supervise directories  
> could be split out and stored elsewhere (presumably on tmpfs) in  
> such environments.

I do that exactly -- /, including /etc, is read-only on most of my  
systems. I put scripts in /etc/supervise so they hit the configuration  
management, and symlink the supervise directory to /var/tmp/run/ 
whatever so it can be read/write.

	Zach