Re: post action

[Charlie Brady <charlieb-supervision@budge.apana.org.au>]

On Fri, 5 Nov 2010, Alejandro Mery wrote:

> Hi, I have a problem with a service [1] which runs fine and handles HUP, TERM
> correctly and sends output to stderr as a good citizen. Unfortunately it
> (re)creates a unix socket with permissions unfit for the purpose, so I have to
> chmod g+w /var/run/thin-*/socket every time. cron gives me a granularity of 1
> minute which still makes the application unreachable for up-to one looooong
> minute.
> 
> The authors don't care because it works fine when daemonizing... and "one
> shall daemonize the daemons"... no comment on that.
> 
> Is there an elegant way of solving this issue with runit?

I don't think it's runit's problem. It's a problem with thin. Since thin
appears to be a daemon written in ruby, you can just patch it.

If it were a binary only application, that you couldn't patch, you could 
use LD_LIBRARY_PRELOAD to load a shim which captures the chmod call, and 
just ignores it if the path matches your socket.

> Thanks,
> Alejandro Mery
> 
> [1] <http://code.macournoyer.com/thin/>
> 
>