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

2018-04-09 Thread Tom H
On Sun, Apr 8, 2018 at 9:35 PM, Christian Kujau wrote: > > I was able to disable journald similar to this: > > systemctl stop systemd-journald-dev-log.socket systemd-journald.socket > systemd-journald.service > systemctl mask systemd-journald-dev-log.socket

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

2018-04-08 Thread Christian Kujau
I was able to disable journald similar to this: systemctl stop systemd-journald-dev-log.socket systemd-journald.socket systemd-journald.service systemctl mask systemd-journald-dev-log.socket systemd-journald.socket systemd-journald.service (I tried to "disable" those services first, but

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

2016-11-21 Thread Tom H
On Sun, Nov 20, 2016 at 7:12 PM, Matthew Miller wrote: > > So that said, if you really want a journald-free system based on > Fedora, you might try uselessd, a "minimized" fork of system. > http://uselessd.darknedgy.net/. We don't include it, but you might be > able to

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

2016-11-20 Thread Matthew Miller
On Sun, Nov 20, 2016 at 07:12:29PM -0500, Matthew Miller wrote: > The journal provides several very useful features. I find > 'systemctl status sshd' (or service of your choice) to be really > useful. The filtered results are also really nice — much easier than > grepping because grep isn't

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

2016-11-20 Thread Matthew Miller
On Thu, Nov 17, 2016 at 04:03:52PM +0100, Franta Hanzlík wrote: > What I want is completely eliminate 'journald' program, of course (if I can > not get rid of the systemd :( Are you trying to solve a particular problem other than distaste for journald? If that's what it is, sure, go for it, but

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

2016-11-20 Thread Tom H
On Thu, Nov 17, 2016, Franta Hanzlík wrote: > On Thu, 17 Nov 2016, Tom H wrote: >> On Thu, Nov 17, 2016, Franta Hanzlík wrote: >>> >>> Eh, excuse for bad formulation. Binary log I can inhibit with >>> specifiing 'Storage=none' in

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

2016-11-17 Thread Franta Hanzlík
On Thu, 17 Nov 2016 19:43:11 +0200 Tom H wrote: > On Thu, Nov 17, 2016 at 5:03 PM, Franta Hanzlík wrote: > > > > Eh, excuse for bad formulation. Binary log I can inhibit with > > specifiing 'Storage=none' in [Journal] section of > >

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

2016-11-17 Thread Tom H
On Thu, Nov 17, 2016 at 8:27 PM, Tom Horsley wrote: > On Thu, 17 Nov 2016 19:53:04 +0200 Tom H wrote: > >> PS: Using non-legacy directives, >> >> module(load="imuxsock" SysSock.Name="/run/systemd/journal/syslog") > > You must be a rsyslog developer Definitely not, LOL >

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

2016-11-17 Thread Tom Horsley
On Thu, 17 Nov 2016 19:53:04 +0200 Tom H wrote: > PS: Using non-legacy directives, > > module(load="imuxsock" SysSock.Name="/run/systemd/journal/syslog") You must be a rsyslog developer, because the last time I tried, I couldn't find the slightest particle of human readable documentation

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

2016-11-17 Thread Tom H
On Thu, Nov 17, 2016 at 5:04 PM, Tom Horsley wrote: > > 1. Make sure you install rsyslog if it isn't already. > > 2. Edit /etc/systemd/journald.conf and set these parameters: > > Storage=none > ForwardToSyslog=yes > > 3. Edit /etc/rsyslog.conf and make sure > $ModLoad

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

2016-11-17 Thread Tom H
On Thu, Nov 17, 2016 at 5:03 PM, Franta Hanzlík wrote: > > Eh, excuse for bad formulation. Binary log I can inhibit with > specifiing 'Storage=none' in [Journal] section of > /etc/systemd/journald.conf. > > What I want is completely eliminate 'journald' program, That's not

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

2016-11-17 Thread Tom Horsley
On Thu, 17 Nov 2016 15:50:24 +0100 Franta Hanzlík wrote: > Nobody knows how to get rid of those unnecessary journald binary logs? I can't get rid of journald, but I can reduce it to nothing more than a proxy, relaying data to rsyslog, which then writes logs in readable text as God intended them:

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

2016-11-17 Thread Franta Hanzlík
On Thu, 17 Nov 2016 15:50:24 +0100 Franta Hanzlík wrote: > > Nobody knows how to get rid of those unnecessary journald binary logs? > > > On Sun, 18 Sep 2016 13:01:49 +0200 > Franta Hanzlík wrote: > > > In previous Fedora distros was (IMHO) right way

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

2016-11-17 Thread Franta Hanzlík
Nobody knows how to get rid of those unnecessary journald binary logs? On Sun, 18 Sep 2016 13:01:49 +0200 Franta Hanzlík 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

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

2016-09-18 Thread Franta Hanzlík
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