| 1 |
Am Mon, 23 Feb 2015 00:41:50 +0100 |
| 2 |
schrieb lee <lee@××××××××.de>: |
| 3 |
|
| 4 |
> Neil Bothwick <neil@××××××××××.uk> writes: |
| 5 |
> |
| 6 |
> > On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: |
| 7 |
> > |
| 8 |
> >> > I wonder if the OP is using systemd and trying to read the journal |
| 9 |
> >> > files? |
| 10 |
> >> |
| 11 |
> >> Nooo, I hate systemd ... |
| 12 |
> >> |
| 13 |
> >> What good are log files you can't read? |
| 14 |
> > |
| 15 |
> > You can't read syslog-ng log files without some reading software, usually |
| 16 |
> > a combination of cat, grep and less. systemd does it all with journalctl. |
| 17 |
> > |
| 18 |
> > There are good reasons to not use systemd, this isn't one of them. |
| 19 |
> |
| 20 |
> To me it is one of the good reasons, and an important one. Plain text |
| 21 |
> can usually always be read without further ado, be it from rescue |
| 22 |
> systems you booted or with software available on different operating |
| 23 |
> systems. It can be also be processed with scripts and sent as email. |
| 24 |
> You can probably even read it on your cell phone. You can still read |
| 25 |
> log files that were created 20 years ago when they are plain text. |
| 26 |
> |
| 27 |
> Can you do all that with the binary files created by systemd? I can't |
| 28 |
> even read them on a working system. |
| 29 |
|
| 30 |
What Canek and Rich already said is good, but I'll just add this: it's not like |
| 31 |
you can't run a classic syslog implementation alongside the systemd journal. |
| 32 |
On my systems, by *default*, syslog-ng kept working as usual, getting the logs |
| 33 |
from the systemd journal. If you want to go further, you can even configure |
| 34 |
the journal to not store logs permanently, so that you *only* end up with |
| 35 |
plain-text logs on your system (Duncan on gentoo-amd64 went this way). |
| 36 |
|
| 37 |
So no, the format that the systemd journal uses is most decidedly *not* a reason |
| 38 |
against using systemd. |
| 39 |
|
| 40 |
Personally, I'm probably going to uninstall syslog-ng, because journalctl is |
| 41 |
*such* a nice way to read logs, so why run something whose output I'll never |
| 42 |
read again? I recommend reading |
| 43 |
http://0pointer.net/blog/projects/journalctl.html for examples of the kind of |
| 44 |
stuff you can do that would be cumbersome, if not *impossible* with regular |
| 45 |
syslog. |
| 46 |
|
| 47 |
HTH |
| 48 |
-- |
| 49 |
Marc Joliet |
| 50 |
-- |
| 51 |
"People who think they know everything really annoy those of us who know we |
| 52 |
don't" - Bjarne Stroustrup |
Archives