fighting the lack of good ideas

always use verbose output when troubleshooting

In my eBook, Debugging and Supporting Software Systems, I wrote about several aspects of submitting good bug reports and support ticket, how to communicate, and more.

If you’re ever troubleshooting a problem, it is universally helpful to enable the most verbose output possible in logging (stdout, stderr, and log files). You may not want it on all the time – but when there are issues, it’s vital.

It’s especially helpful if, as a group, you are involved in a ticket smash.

Verbose output saved me just this week in seeing that a bind mount I thought was working properly was not (and causing an entire install to fail).
Thanks, –verbose 🙂