On 2019-09-20 20:05:53 +0200, Christian Göttsche wrote: > In my opinion the advantages (more robust triggering on non 24/7 systems, > more security by service hardening options) outweigh.
For non 24/7 systems, there is anacron. > > The error message is in the systemd logs, but this is not sufficient. > > Logs are fine for informational messages in order to debug or to try > > to find the cause of a problem, but for something that requires a > > manual intervention like here, the user must be informed, otherwise > > the problem may remain unnoticed for a long time. > > You can monitor 'systemctl is-system-running', or use something like > the following timer: > > #### timer > [Unit] > Description=Daily log warnings report > After=systemd-journald.service > [Timer] > OnCalendar=*-*-* 23:59:40 > AccuracySec=10s > Persistent=true > [Install] > WantedBy=systemd-journald.service > > #### service > [Unit] > Description=Daily log warnings report > [Service] > Type=oneshot > ExecStart=/bin/sh -c "/bin/journalctl --priority error --since today | > mail -s 'log warnings daily report' root" > KillMode=process There is no "error" priority. Perhaps you meant "err", but that's useless since it is too low: there are many non-fatal errors in the logs. The "crit" priority gives only interesting errors, i.e. those that may affect the system (and security alerts); for instance, exim does that when /var/log/exim4/paniclog has non-zero size (this happened when it could not bind to port 25). I think that logrotate should use that when it cannot rotate a log file. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
