DragonFly BSD
DragonFly kernel List (threaded) for 2005-02
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: rc and smf

From: "George Georgalis" <george@xxxxxxxxx>
Date: Thu, 24 Feb 2005 13:33:18 -0500

Whoa, I missed a whole thread while I was writing my post.

On Thu, Feb 24, 2005 at 01:12:38PM -0500, George Georgalis wrote:
>For those considering (and those with prejudice), I'd like to remind
>that, the people who use above softwares are happy, if quiet. Also,
>there is excellent support on their respective lists too, especially if
>you don't put down the software while there, do the homework and remain
>receptive to the criticize you solicit.

While supervise has an options to start a program only once (ie
no restart); it is generally designed to restart a daemon (that is
not necessarily perfect and stops, or is inadvertently killed by an
unexpected system event). So "one run daemons" may be better invoked
outside of supervise, by a program such as runit or init.

I don't know how much better BSD init is then sysvinit, but I've really
never experienced a problem with either. That said I would not embrace
BSD init purely because of its historical use. I'd consider that in
evaluating a replacement, but make my own assessment. Or review someone
else's. The issue to "available development time" ratio is defiantly a
factor here.

Issues such as restarts the admin is unaware of, memory or cpu load
during runtime or start; these are the issues that make supervise and
multilog so useful. They can all be addressed, with much flexibility to
the admin, through proper run and log/run scripts. 

// George

George Georgalis, systems architect, administrator Linux BSD IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:george@xxxxxxxxx

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]