| 1 |
On Sun, Feb 22, 2015 at 6:41 PM, lee <lee@××××××××.de> wrote: |
| 2 |
> |
| 3 |
> Neil Bothwick <neil@××××××××××.uk> writes: |
| 4 |
> |
| 5 |
> > On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: |
| 6 |
> > |
| 7 |
> >> > I wonder if the OP is using systemd and trying to read the journal |
| 8 |
> >> > files? |
| 9 |
> >> |
| 10 |
> >> Nooo, I hate systemd ... |
| 11 |
> >> |
| 12 |
> >> What good are log files you can't read? |
| 13 |
> > |
| 14 |
> > You can't read syslog-ng log files without some reading software, |
| 15 |
usually |
| 16 |
> > a combination of cat, grep and less. systemd does it all with |
| 17 |
journalctl. |
| 18 |
> > |
| 19 |
> > There are good reasons to not use systemd, this isn't one of them. |
| 20 |
> |
| 21 |
> To me it is one of the good reasons, and an important one. Plain text |
| 22 |
> can usually always be read without further ado, be it from rescue |
| 23 |
> systems you booted or with software available on different operating |
| 24 |
> systems. It can be also be processed with scripts and sent as email. |
| 25 |
> You can probably even read it on your cell phone. You can still read |
| 26 |
> log files that were created 20 years ago when they are plain text. |
| 27 |
> |
| 28 |
> Can you do all that with the binary files created by systemd? |
| 29 |
|
| 30 |
Yes, you can. |
| 31 |
|
| 32 |
> I can't even read them on a working system. |
| 33 |
|
| 34 |
If that's true (which I highly doubt, more probably you don't know how to |
| 35 |
read them), then it's a bug and should be reported and fixed. |
| 36 |
|
| 37 |
Regards. |
| 38 |
-- |
| 39 |
Canek Peláez Valdés |
| 40 |
Profesor de asignatura, Facultad de Ciencias |
| 41 |
Universidad Nacional Autónoma de México |
Archives