cruise -d should not swallow output or return 0 on error
Reported by Jeremy Lightsmith | July 29th, 2008 @ 07:23 PM
it should instead output a stack trace or at least send it into the cruise.log
basically, if we're trying to debug an init script and it's blowing up, it's very hard to debug, and it should be easier.
Comments and changes to this ticket
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
