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.
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Jeremy Lightsmith