Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

systemd's syslogd replacement supports JSON output

freedesktop.org

Post reply on HN
Print view View original

51–54 of 54 posts

Re: systemd's syslogd replacement supports JSON output

#51

Post by fosap »

benbataille wrote: post #42
fosap wrote: post #36

Earlier quoted context omitted.

something that was not necessary. Init scripts can be nice and clean [1]. And yes, I'm all for a init replacement. Something new, nice and clean. But I take the shell script hackery over a dbus dependency. But that's just my personal opinion. I have neither used it nor looked at the code, but [2] seems to be what I want. It's by the libdietc author, so i expect the code to be small, elegant and not maintained very we…

That's again a myth. There is no dbus dependency. You can use dbus to do activation but you don't have to. Now, there is a dependency on libdbus which just means systemd is using the dbus serialisation format for its ipc (which, I repeat, don't have to happen over dbus).

Systemd seems to be quite mysterious, because the myth of the dbus dependency comes from the lead developer trying to debunk myths.

http://0pointer.de/blog/projects/the-biggest-myths.html

>When you build systemd, it only requires three dependencies: glibc, libcap and dbus.

In the paragraph "bloated".

Re: systemd's syslogd replacement supports JSON output

#52

Post by benbataille »

fosap wrote: post #51
benbataille wrote: post #42

Earlier quoted context omitted.

That's again a myth. There is no dbus dependency. You can use dbus to do activation but you don't have to. Now, there is a dependency on libdbus which just means systemd is using the dbus serialisation format for its ipc (which, I repeat, don't have to happen over dbus).

Systemd seems to be quite mysterious, because the myth of the dbus dependency comes from the lead developer trying to debunk myths. http://0pointer.de/blog/projects/the-biggest-myths.html >When you build systemd, it only requires three dependencies: glibc, libcap and dbus. In the paragraph "bloated".

It's because I'm not really precise (but neither is Lennart). Technically, libdbus is a part of dbus. It allows two applications to communicate with each other using the dbus serialisation and abstracts the transport layer. You can use it over a Unix socket and then it's just a serialisation format like any application using IPC would need. Then, using dbus is no more stupid than anything else. Actually, it's pretty clever as there already is quite a lot of tools understanding this format.

However, libdus is not what people usually talk about when they talk of dbus. The core part of dbus and what could bother server administrator is the message bus daemon which allows any applications to expose their functionalities and talk to any others. Now, systemd can use the message bus to allow applications to ask for service activation. But, it's not required and you can run the init system without it.

Re: systemd's syslogd replacement supports JSON output

#54

Post by weitzj »

tzs wrote: post #53
weitzj wrote: post #11

But what if it's used for evil? :0

It doesn't look like they are using Douglas Crockford's JSON implementation, so using it for evil is probably OK.

Thanks for the upvote. I did not know my karma would get busted for my comment.
Post reply on HN