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'.
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'...
MS makes it much to painful to do hat -- 1 error / page, everything in
300 separate queries ... ug!
> 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 -- had to label ng3x taboo, so it won't overwrite
a working config with a non working config...
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org