On Wednesday 19 September 2012, Per Jessen wrote:
Linda Walsh wrote:
Cristian Rodríguez wrote:
El 15/09/12 11:49, Per Jessen escribió:
I do want to log, but I've looked at the journal already and didn't see anything that wasn't already in /var/log/messages, /var/log/mail etc. Seems like a duplication of effort and a waste of space in /var/log/journal. (which afaict can just be deleted).
It is significantly more powerful than traditional logging:
For example
journalctl /usr/bin/foo --> get messages from program foo
journalctl /dev/sda --> hard-drive problems ?
journalctl -p error --> only errors
--- I assume the full power of linux's text utilities can be used on them - like grep, sort, awk, perl... vim...
Having logs recorded in a non-text binary format tends to make MS logs out-a-sight, out-a-mind, where as I often go and poke around in /var/log and look to see if I notice anything 'new'.
Same here.
If I can't look at the whole stream as a text (messages, warnings, etc), I don't get a field for what is right or wrong behavior and certainly wouldn't be able to pick out an anomaly if I had to query each item separately -- that global view is a good way to look for 'warts'...
I think I tried "journalctl" - without arguments you get the whole log (afaict).
Unfortunately you can do this only on machines where journalctl is installed/available. I assume that you can't read the journald logs on most existing systems.
Currently it is not a full replacement for syslog but I suggest you to check it out.
I tend to use ngsyslog for the filtering benefits. -- really has some powerful filtering in the 2.x line
Ditto - also much easier to configure than rsyslog.
-- Per Jessen, Zürich (12.4°C)
cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org