you do NOT need to write all your programs together to make them work together. [LWN.net]

you do NOT need to write all your programs together to make them work together.

Posted Jan 31, 2013 19:41 UTC (Thu) by dlang (✭ supporter ✭, #313)
In reply to: you do NOT need to write all your programs together to make them work together. by sorpigal
Parent article: Poettering: The Biggest Myths

remember, this isn't just systemd's internal logs, systemd intercepts logs that the apps write to syslog and turn them into this new structure as well.

(Log in to post comments)

you do NOT need to write all your programs together to make them work together.

Posted Jan 31, 2013 20:42 UTC (Thu) by davidstrauss (subscriber, #85867) [Link]

> remember, this isn't just systemd's internal logs, systemd intercepts logs that the apps write to syslog and turn them into this new structure as well.

Just keep omitting that systemd's journal forwards the entries *unaltered as syslog*, and you might convince some people that the journal breaks their traditional syslog toolchain.

you do NOT need to write all your programs together to make them work together.

Posted Jan 31, 2013 20:46 UTC (Thu) by dlang (✭ supporter ✭, #313) [Link]

look at the context, I am replying to someone explaining how presenting how the journal deals with logs differently could avoid antagonizing people. I am just pointing out that his statement is not complete, it's not just the internal journald logs that are involved.

you do NOT need to write all your programs together to make them work together.

Posted Feb 1, 2013 1:21 UTC (Fri) by davidstrauss (subscriber, #85867) [Link]

> look at the context, I am replying to someone explaining how presenting how the journal deals with logs differently could avoid antagonizing people. I am just pointing out that his statement is not complete, it's not just the internal journald logs that are involved.

I'm aware of the context. I just think it's disingenuous to use how the systemd's journal maintains its own data structures to imply some change happens that creates complexity for syslog users.

Use of internal data structures is true of any log daemon, including rsyslog. Saying that the journal "turn[s] them into this new structure as well" implies that the syslog messages emitted by the journal are not identical to the messages sent in, which is false.

The journal goes beyond syslog, but it does not get in its way or force users to change any existing applications, monitoring, or workflows.

When we updated our configurations for Fedora 17 (the first release with the journal), we didn't have to touch anything to continue getting the same syslog messages we got before in the same places we had always looked for them.