> > Yes, it's a problem with the monitoring solution trying to do the job of > the unicorn master process. Unicorn is designed to use the master > process and there's no other way to do what Unicorn does without it. > > The unicorn master process itself should be very robust and never fail > during normal operation (upgrades may break it if things go really > wrong, but you already pay attention to what you're upgrading, right?). >
I'm not concerned about the unicorn process failing - more i use daemon tools on boot and to make sure the process comes alive properly at boot and because daemon tools has a simple and intelligent interface that doesn't have me writing blue-pill conf files or monit conf files. That said - it may be enough to monitor that wrapper script in this case. -- make haste slowly \ festina lente \ - mobile +1_415_632_6001 [email protected] http://robotarmyma.de _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
