| 1 |
On Sun, Feb 22, 2015 at 6:41 PM, lee <lee@××××××××.de> wrote: |
| 2 |
> |
| 3 |
> To me it is one of the good reasons, and an important one. Plain text |
| 4 |
> can usually always be read without further ado, be it from rescue |
| 5 |
> systems you booted or with software available on different operating |
| 6 |
> systems. It can be also be processed with scripts and sent as email. |
| 7 |
> You can probably even read it on your cell phone. You can still read |
| 8 |
> log files that were created 20 years ago when they are plain text. |
| 9 |
|
| 10 |
Doing any of that stuff requires the use of software capable of |
| 11 |
reading text files. It isn't like you can just interpret the magnetic |
| 12 |
fields on your disk with your eyes. |
| 13 |
|
| 14 |
Sure, there are a lot more utilities that can read text files than |
| 15 |
journal files, but you just need to arrange to have them handy. |
| 16 |
They'll be ubiquitous before long since every distro around will end |
| 17 |
up needing them. |
| 18 |
|
| 19 |
> |
| 20 |
> Can you do all that with the binary files created by systemd? I can't |
| 21 |
> even read them on a working system. |
| 22 |
> |
| 23 |
|
| 24 |
You just type journalctl to read the live system logs. For offline |
| 25 |
use you just type journalctl --file=filename. Or you can just run |
| 26 |
strings on the file I imagine if you're desperate. If it doesn't work |
| 27 |
on a "working system" then your system isn't working. |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Rich |
Archives