Yeah application logging has been way to diverse in Linux. Ideally all logs should be written to /var/log or in its subdirectories. For example X.org writes a lot of its log files inside the Users home directory.Not really, other than a report from cruft_ng on a system with history. Overall, application logging has always been diverse and not strictly contained to /var/log. Reading the config files of logrotate and rsyslog will give some clues of what they handle, as hinted /etc/logrotate.d/ is the list for any particular system. Wizard's short list is longer than mine.any suggestion on how to carry out the audit of legacy programs that may still use the old way?
Some would disagree with you on that.
Journalctl is a huge improvement and is now very useful. I've added a click on a genmon panel on systems with many automounts to tell me their status, after hiding them from display with udev. So, “noise Mounted” or “noise Unmounted” blips onto the screen and then fades...Code:
notify-send "noise $(journalctl -g -.noise -n 1 --no-pager | cut -d " " -f 6)"
Journalctl writes log files in binary format, hence there are issues that come up when commands like grep/egrep/less are used. This is especially important when the system does not boot up.
Additionally Journalctl is tied at hip with systemd which causes a lot of people to have adverse reaction to it.
Statistics: Posted by DebianFox — 2024-11-01 06:51 — Replies 8 — Views 529