majorair
10-25-2006, 01:11 AM
Hey all!
I'm wondering about the best way to start daemons up on boot, and how best to keep them alive after startup...
I'm using Pen along with Mongrel_Cluster to serve up an application, and I have Apache fronting that and handling vhosting. I haven't used mod_proxy_balancer, because I haven't spent enough time to get Apache2.2 running yet. I may get rid of Apache completely when I do my final deploy, for speed and memory purposes.
Anyway, I need to start my Pen process on boot, and then I want to be able to make sure that it stays alive afterwards. I've used DJB's daemontools in the past, but the Rimuhosting staff told me that this was evil... Since they know way more than me, I'm hoping that there is a better way.
Peter pointed me here: http://plope.com/Members/chrism/debian_rc_local_equiv which is a great way to start the process, but how should I make sure it stays alive, and restart it if it dies? Is there some way cool setup I'm not aware of?
Thanks!
Matt
I'm wondering about the best way to start daemons up on boot, and how best to keep them alive after startup...
I'm using Pen along with Mongrel_Cluster to serve up an application, and I have Apache fronting that and handling vhosting. I haven't used mod_proxy_balancer, because I haven't spent enough time to get Apache2.2 running yet. I may get rid of Apache completely when I do my final deploy, for speed and memory purposes.
Anyway, I need to start my Pen process on boot, and then I want to be able to make sure that it stays alive afterwards. I've used DJB's daemontools in the past, but the Rimuhosting staff told me that this was evil... Since they know way more than me, I'm hoping that there is a better way.
Peter pointed me here: http://plope.com/Members/chrism/debian_rc_local_equiv which is a great way to start the process, but how should I make sure it stays alive, and restart it if it dies? Is there some way cool setup I'm not aware of?
Thanks!
Matt