Re: post action

[Laurent Bercot <ska-supervision@skarnet.org>]

> 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.

 If you want to avoid patching software or doing ugly things like
intercepting syscalls (YMMV, but to me it IS ugly :P), depending on
your OS, you could set up an additional service that watches the
socket creation and automatically chmods it to the right permissions.

 Unfortunately, Unix does not offer any portable way to be notified
of FS operations, so the code of that additional service would have to
be OS-specific. For instance, you'd use "inotify" on Linux and "kevent"
on BSD.

 Or you would have to resort to polling - which is exactly what cron does
anyway, except using a specific service would let you have control over
the polling granularity. But I am definitely not going to suggest that.
(What is the lesser evil between polling and intercepting syscalls? now
that's an interesting question of faith. :))

-- 
 Laurent