: I'm curious as to why not. For the SME Server, we've moved from : supervise to runit (http://smarden.org/runit) as it has all of the : features of supervise (and more), without djb's licensing issues. : : IMO supervise/runit is clean and simple and it works.
I will be glad to check out runit and see what I think. I don't have too much of a personal bias against it - it's mostly that a lot of these systems we were dealing with were controlled and managed by end users who had a minimal familiarity with Linux systems. init.d scripts like that are commonplace, relatively obvious, and need to be dealt with for other processes. My personal computer (which is giving me the problem) has that init.d setup because I need to verify the setup prior to deploying something similar in the field. I do have supervise running on the main server for a couple things so I'll check out what runit offers in it's place -- Matthew Harrell Nature abhors a vacuum. Bit Twiddlers, Inc. Then again, so does my cat. [EMAIL PROTECTED]
