On 02/01/15 10:40, Avery Payne wrote:
On Thu, Jan 1, 2015 at 3:39 PM, Luke Diamand <[email protected]> wrote:
Caution, a shameless plug follows:
If you are willing to share the contents of your scripts with a very
permissive license, I would like to see them and possibly incorporate the
ideas into my current project.
https://github.com/luked99/supervision-scripts
Quite a few things seem to be subtly (but trivially) wrong in the
instructions to get this going, so although it's actually quite
straightforward now I've worked out what I'm doing, it took a lot longer
than I expected.
The instructions do need to be updated a bit. Once it is up and running
it's not so bad; in fact, it probably wouldn't take too long to update the
instructions (hint hint).
The instructions should just tell you to install the debian package
("runit-initscripts" ?). Is that possible? I might be able to write such
a package if it was the right way to go.
For example, the service directory in the instructions is /service, but
debian now uses /etc/service (OK....), but the example [123] scripts
shipped in /usr/share/doc still use /service, and at least in my case,
having a symlink in /service resulted in weird error messages which went
away once I fixed this.
I currently have /service -> /etc/service on a system at home and haven't
had any issues. What are you seeing? What version of runit do you have?
Sorry, I didn't record the errors at the time (I assumed it was just
user-error on my part). runit is 2.1.2-3.
Are there any plans to create a debian package that would just put all the
bits in the right place, so you can simply install the package and have it
then use runit-init as /sbin/init ?
The problem isn't the package; the problem is the size of Debian itself.
Or rather, the fact that Debian is a very, very large organization, and to
make it work properly, all of the package maintainers would have to be
"hassled" into supporting the arrangement. This is one of the many reasons
I started the supervision-scripts project, because Debian was lacking a
reasonable set of management scripts out-of-the-box.
That's quite a hard problem to solve...!
