"thin -d" always returns 0 (success) even if servers failed to start/stop
Reported by Iñaki Baz Castillo | December 21st, 2009 @ 01:28 PM | in Future
Note that this bug is different than #119.
When using -d option to daemonize the server(s) thin command always returns 0 even if the server(s) start action failed. This is really annoying when working with init service scripts as 0 means "the server has started correctly and it's running now".
I will try to code a patch similar to what I did for #199.
No comments found
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »