Re: prong: keep your daemons alive and report if they are fataly wounded.

2012-08-24 Thread Han Boetes
Gilles Chehade poolp.org> writes: > Also, restarting a daemon that has crashed because of an exploit means > you expose it again with maybe less luck next time (kindly reminded by > mail Right, that's a valid point. In that case you'd only want an email to be sent. Either way, my script is from

Re: prong: keep your daemons alive and report if they are fataly wounded.

2012-08-24 Thread Gilles Chehade
On Fri, Aug 24, 2012 at 10:21:12PM +0200, Gilles Chehade wrote: > > Unless things have changed, I was told in 2008 that this kind of > tools is not going to hit our tree because it's not unix ;-) > Also, restarting a daemon that has crashed because of an exploit means you expose it again with ma

Re: prong: keep your daemons alive and report if they are fataly wounded.

2012-08-24 Thread Gilles Chehade
On Fri, Aug 24, 2012 at 08:53:55PM +0200, Han Boetes wrote: > Hi, > Hi Han, > This is my idea of how to implement this functionality. Rather > simple and transparent. If you like the idea but think you can > make a better implementation feel free to make it.. > For what it's worth, I had a sim

prong: keep your daemons alive and report if they are fataly wounded.

2012-08-24 Thread Han Boetes
Hi, This is my idea of how to implement this functionality. Rather simple and transparent. If you like the idea but think you can make a better implementation feel free to make it.. Yes there are other implementations that can do about the same, but I wanted to write something the OpenBSD way. I