Posted on Fri 25 February 2022

log more on failure than success

When something goes wrong, especially (but not limited to) at startup, you should log an error message that is as informative as possible. In particular, if your service has parameters that might conflict with any other running process –say, it wants to listen to a particular port– you should have the error message mention all of those details.

It’s even better if the failure does a little diagnostic and tells you what other process is using that port.

This message brought to you by the Campaign for More Informative Error Messages. -30-

© -dsr-. Send feedback or comments via email — by continuing to use this site you agree to certain terms and conditions.

Built using Pelican. Derived from the svbhack theme by Giulio Fidente on github.