[14:42] <foo> Can I delete stuff in /var/log/journal? I've got 4G in there
[14:45] <rfm> foo, I think the approved way is to run one of the "journalctl --vacuum-..." commands, like "journalctl --vacuum-size=1G:
[14:46] <foo> rfm: ohh, I've never ran that before
[14:46] <rfm> foo, well, neither have I, but I read about it in the docs
[14:48] <rfm> foo, you can also tune the parms in /etc/systemd/journald.conf to control the auto vacuuming, but it might be better to actually look at the logs and see if there's something spewing out lots of messages and fix that  
[14:49] <foo> rfm: ohhh, good idea.
[14:51] <foo> rfm: when you say "look at the logs" are we talking about logs in /var/log/journal/ or syslog ? Probably the former
[14:52] <rfm> foo, yeah, journalctl to display the journal logs, since that's the place you're filling up.. though the syslog files probably duplicate the same info
[14:54] <rfm> foo, I keep thinking I should reconfigure syslog not to keep the /var/log/*.log to stop the duplication, but have never got around to it
[14:56] <foo> rfm: we've got a cron job that runs every minute. It looks like every minute it generates 6 lines in the journal log. Fast forward to years of running this... and that might explain my 4G of data in here :) 
[15:03] <rfm> fpo, looks like the default size for auto vacuum is 4G, so I guess any system that runs long enough will get there.  Probably worth trying to figure out how to make that cron job only put out messages if something goes wrong, just to cut down then noise.  I think cron jobs always log at least a couple messages, though. Maybe a systemd timer unit would be quieter?
[15:53] <foo> rfm: thanks, interesting. Will have to investigate. Appreciate the sounding board, thank you. :)