Notices by :ffxivmsq_comp: Efertone :verifiedtrans: (efertone@slippy.xyz)

@dushman@den.raccoon.quest @adiz@soc0.outrnat.nl @emma@niscii.xyz @jeff@misinformation.wikileaks2.org Yes, full vacuum is slow and explicite locks the table while it's working on it, meaning for example, can't record new notes in the database. So be careful with that.

@emma@niscii.xyz @adiz@soc0.outrnat.nl @dushman@den.raccoon.quest I think the easiest one (if you are using systemd, journalctl is one of the best friends):sudo journalctl -u cron | grep "scriptname"
It will show you when they were executed (and what user):# Run by misskey user Sep 17 20:30:01 slippy CRON[389091]: (misskey) CMD (/home/misskey/kiki fetch && /home/misskey/kiki publish) # Run by root (creates daily mysql dumps) Sep 17 01:00:01 slippy CRON[246758]: (root) CMD (/root/backup/backup.database.mysql.sh) # Run by root (creates weekly basebackup for WAL) Sep 17 02:00:01 slippy CRON[252575]: (root) CMD (/root/backup/backup.database.postgresql.sh) # Run by my own user to clean up old remote files through API calls. Sep 17 03:00:01 slippy CRON[258304]: (efertone) CMD (/home/efertone/slippy-maintenance/clean-old-remote-files.py)
It will not record the exist status, but I get an email always when stderr is not empty.

Hope it helps.