Dmitry Bogatov schrob: > No, I did not consider this aspect. Thank you. > But since runscripts are conffiles, admin can add line > > chown -R trusted_user:0 /run/runit/supervise/foo > > into /etc/sv/foo/run, and they will be preserved during upgrade. Not > that staightforward, but still solution. Is it acceptable?
That means they'll get a conffile prompt if/whe the maintainer changes
the run file. Personally, I'd prefer linking /etc/sv/foo/supervise to a
place of my choosing and expect that link to be preserved. Not sure how
others would feel, or how they'd try to deal with the issue.
<rambling = on>
I'm still trying to figure out the best way to split things for my
personal needs (which include service definitions being rsync()able
across machines), and in the middle of another reorganization. So I
clearly haven't found the ideal layout yet either. :(
FWIW, I really liked having a ramdisk on /etc/service and copying
/etc/sv/* there. Biggest issue with that was getting updates across
cleanly. I wish runsvdir had a mode to "kill -TERM your runsvdir
children, wait for them to exit, then exit yourself." Maybe the answer
will be implementing that. Or maybe a 2nd attempt at scaffolding to move
services out of the way, wait for them to stop, move the new definitions
in place. Or maybe have /etc/sv be the ramdisk. Aaargh. :D
</rambling>
Anyway, I clearly have no bronze bullet, sorry.
cheers,
Jan
signature.asc
Description: PGP signature
