The Debian init system general resolution returns

Posted Nov 2, 2014 21:08 UTC (Sun) by johannbg (guest, #65743)
In reply to: The Debian init system general resolution returns by nix
Parent article: The Debian init system general resolution returns

As far as I know this..

"That's going to be changed soon, it'll be possible to configure per-service symlinks for the /dev/log."

is not happening upstream so if you are going to implement this you will have to implement this as somekind of downstream hack

The Debian init system general resolution returns

Posted Nov 3, 2014 1:22 UTC (Mon) by dlang (guest, #313) [Link] (4 responses)

that was a statement made here on LWN by a systemd supporter in a thread telling me that my complaints about journald were unjustified and that systemd was not unresponsive.

The Debian init system general resolution returns

Posted Nov 3, 2014 1:45 UTC (Mon) by rahulsundaram (subscriber, #21946) [Link]

Just like bugs without proper bug reports, assertions about a project's roadmap unaccompanied by citations by non project developers have less credibility and should not be relied upon blindly.

The Debian init system general resolution returns

Posted Nov 3, 2014 1:49 UTC (Mon) by Cyberax (✭ supporter ✭, #52523) [Link]

I'll find Lennart's post about this later.

The Debian init system general resolution returns

Posted Nov 3, 2014 19:19 UTC (Mon) by Cyberax (✭ supporter ✭, #52523) [Link] (1 responses)

Here it is:
http://lists.freedesktop.org/archives/systemd-devel/2014-...

> In recent versions of systemd you can just override Symlinks= in
> systemd-journald-dev-log.socket and set it to the empty array, and
> then add Symlinks=/dev/log in syslog.socket instead, which should
> change /dev/log from being directed to the journal, to beign directed
> directly to your syslog instance. But note again, that will lose much
> of the early-boot loggind that way. Also "systemctl status" of course
> won't show you any logs anymore (or at least incomplete ones).

The Debian init system general resolution returns

Posted Nov 3, 2014 23:07 UTC (Mon) by johannbg (guest, #65743) [Link]

This just tells it dont symlink /dev/log to /run/systemd/journal/dev-log ( systemd-journald-dev-log.socket ) but symlink it to /run/systemd/journal/syslog ( syslog.socket ) instead so this is per service how?

And you probably can simply achieve the same breakage ( although untested ) by fiddling with existing ListenDatagram= entries in journal/syslog.socket for example something like removing ListenDatagram=/dev/log in systemd-journald.socket and add it to syslog.socket instead.