configctl not showing errors in Backend Log

Started by CJ, June 25, 2023, 03:11:56 PM

Previous topic - Next topic
A recent thread got me looking at the automated SMART testing for my drive.  In the course of this I also started digging into the automated zfs maintenance.

It turns out that none of these actions had been occurring because I didn't realize they needed parameters.  While one can argue that the zfs job parameters are indicated in the documentation, the SMART testing isn't even in the list.

Leaving aside the docs and UI design, why do so many of the cron options call commands that include "; exit 0" and even on the ones that don't, why does the Backend Log either report nothing or a returned OK message?