On Thu, Nov 17, 2016, Franta Hanzlík <franta(a)hanzlici.cz> wrote:
On Thu, 17 Nov 2016, Tom H <tomh0665(a)gmail.com> wrote:
> On Thu, Nov 17, 2016, Franta Hanzlík <franta(a)hanzlici.cz> wrote:
>> Eh, excuse for bad formulation. Binary log I can inhibit with
>> specifiing 'Storage=none' in [Journal] section of
>> What I want is completely eliminate 'journald' program,
> That's not possible. You need journald as an rsyslog forwarder.
Tom thanks for reply.
It seems to me, as there in conjunction with systemd
somehow often occurs "That's not possible".
But is not possible use for this (somehow) systemd option
I've just tried "systemd.log_target=kmsg" on the kernel cmdline with
rsyslog set up and it logged to "/var/log/" but "journalctl -k" has
some log lines that aren't there with the default "journal-or-kmsg"
setting. Perhaps "systemd.log_target=" sets the location that systemd
logs to _at_boot_ rather than a runtime target, especially since
journald has its own kernel cmdline settings that look like
And earlier, I think even in Fedora 21, it was possible to use the
"--log-target=syslog" - I think, this option was served just for this
purpose. Where has she gone? Why now has been dropped?
The last version to have "--log-target=syslog" was 215. I suspect
that, like "--log-target=kmsg", it didn't mean that journald was
Sorry for this questions, systemd documentation poorly (rather not
all) describe this.
systemd is, in general, well-documented but in this instance
"--log-target=" isn't explained clearly.