Date: Fri, 19 Sep 2003 21:45:45 +0200 From: Clement Laforet <sheepkiller@cultdeadsheep.org> To: "Clemens Fischer" <ino-qc@spotteswoode.de.eu.org> Cc: freebsd-ipfw@freebsd.org Subject: Re: Divert code Message-ID: <20030919214545.6c18f204.sheepkiller@cultdeadsheep.org> In-Reply-To: <oexgre1s.fsf@ID-23066.news.dfncis.de> References: <20030916235808.X92689-100000@skywalker.rogness.net> <20030917175249.4df78d7d.sheepkiller@cultdeadsheep.org> <he3bur8h.fsf@ID-23066.news.dfncis.de> <20030917215628.44bd61f7.sheepkiller@cultdeadsheep.org> <oexgre1s.fsf@ID-23066.news.dfncis.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19 Sep 2003 17:30:17 +0200 "Clemens Fischer" <ino-qc@spotteswoode.de.eu.org> wrote: > naa, that's not in the least dirty. i've been a happy user of the > daemontools for quite some time now, it's a very helpful kit. It's not dirty to try to keep your daemon up. Like you, I use daemontools on critical daemon who need to be working all the time, like logs dispatchers, but we need to know why it dies. supervise is a tools, not a solution. Using daemontools is a good way to not be awaken during the night :-) In this particulary case, I probably make the daemon catch signals to crash "gracefully" and remove divert rule before dying. IDS are very helpful but they mustn't cause a downtime, IMHO. regards, clem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030919214545.6c18f204.sheepkiller>