Re: how to correctly log without journald (and its blobs)?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Nobody knows how to get rid of those unnecessary journald binary logs?


On Sun, 18 Sep 2016 13:01:49 +0200
Franta Hanzlík <franta@xxxxxxxxxxx> wrote:

> In previous Fedora distros was (IMHO) right way to log only to syslog,
> without journald and its (for me) unwanted annoying binary logs, by using
> configuration as:
> 
> *) Set systemd log target to syslog:
> systemd.log_target=syslog (syslog-or-kmsg)  ---- on kernel cmdline
> systemd.default_standard_output=syslog      --/
>    and
> LogTarget=syslog                            ---- in systemd.conf
> DefaultStandardOutput=syslog                --/
> 
> *) configuring rsyslog to listen on /dev/log unix socket:
> $SystemLogSocketName /dev/log                     ------ in rsyslog.conf
> $ModLoad imuxsock                                 ----/
> $OmitLocalLogging off                             ---/
> $AddUnixListenSocket /run/systemd/journal/syslog  --/(legacy directives)
> $AddUnixListenSocket /run/systemd/journal/socket  -/
> $AddUnixListenSocket /run/systemd/journal/stdout  /
> (not sure when all last three directives needed)
> 
> *) prevent to run journald:
> systemctl mask systemd-journald.service
> (and maybe mask systemd-journal-flush.service)
> 
> And it works fine.
> But in actual Fedora 24 in systemd man page values syslog-or-kmsg and
> syslog are missing in LogTarget option. As systemd/journald man pages
> say hardly anything about exact mean of appropriate configuration for
> this purpose, then please when someone more knowledgeable can advise:
> 
> - where to direct the systemd output? Maybe to kmsg an then read it in
> rsyslog via imklog?
> (rsyslog should have also imkmsg module, but is not in rsyslog-8.12.0-3.fc24)
> 
> - what about /run/log/journal/.../system.journal ?
> On my test F24 system it have open rsyslogd, abrt-dump-journal-oops and
> abrt-dump-journal-xorg (no need for these last two) processes. Uses it
> also something else?
> 
> - what about /run/systemd/journal/{dev-log,socket,stdout} unix sockets?
> Should rsyslogd listen on them?
> 
> - /dev/log seems be now symlink to /run/systemd/journal/dev-log socket
> (as defined by systemd-journald-dev-log.socket) Should it be left
> (because now something sends to /run/systemd/journal/dev-log), or can
> be /run/systemd/journal/dev-log removed?
> 
> Thanks in advance for some clarification about this.
> Franta Hanzlik
-- 
Thanks, Franta Hanzlík
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux