Until recently (last update? 2.1.3?), any manually added cron jobs for SiteWorx accounts (non-IWorx) used to announce themselves as having executed in the next morning’s LogWatch. That’s not happening anymore (unless, of course, the jobs just aren’t running - which isn’t the case as far as I can tell).
Did something change with the reporting of Cron jobs via the LogWatch?
JB, logwatch is just a tool bundled with many distros and we don’t touch it whatsoever. Maybe it was updated at some point by the distro and that changed the default settings?
I know that at one point, in regards to the LogWatch reporting for the vpopmail application, the implementation IWorx used in one release created a different output in the logwatch than another point release (e.g. one release showing every authentication request to popmail, and another not showing them).
I wasn’t sure if there was some manipulation similar with the handling of cron job reporting between recent point releases or not.
Doubtufl, it seems like more of a logwatch specific issue (like some config change in logwatch). How were the accounts “announced”? Via an /etc/passwd change?
An existing SiteWorx account creates a cron job. The next (and subsequent) morning’s LogWatch lists (‘announces’) that that job (and any other non-IWorx ones) executed.
At least, that’s what used to happen. It was nice to get that listing of cron executions, even if only as a reminder of the current jobs on the box.