Recent Features
| |||||||||||||
Have you read the document?Have you read the document?Posted Nov 20, 2011 20:02 UTC (Sun) by quotemstr (subscriber, #45331)In reply to: Have you read the document? by khim Parent article: The Journal - a proposed syslog replacement
> Have you read the design doc? This is exactly what journald does.
Except that, AIUI, the goal is to eventually have journal-only logging for some facilities. I don't want that to ever come to pass.
> attach it to the existing textual file
Why not? The index could point into a particular offset in a textual log, or just duplicate the contents of the textual log. The point is to ensure that all logs can be queried with plain-text tools and to _optionally_ provide richer information for these logs. The nightmare scenario is for some messages to appear only in the journal and for other messages to appear only in syslog files.
> stupudity beyond comprehension
Can we try to maintain *some* level of decorum here?
(Log in to post comments)
Have you read the document? Posted Nov 20, 2011 20:13 UTC (Sun) by khim (subscriber, #9252) [Link] > attach it to the existing textual file Because these files are already processed by quite a few different programs stitched together in non-obvious ways. To hope that you can keep all that synchronized... I'll wish you luck. The nightmare scenario is for some messages to appear only in the journal and for other messages to appear only in syslog files. If I understand correctly all messages pass the journald but plain old syslogd messages go to syslogd too. This means journald keeps everything no matter what.
|
|||||||||||||