Gentoo Archives: gentoo-user

From: covici@××××××××××.com
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] systemd seems to have broken logwatch
Date: Thu, 22 May 2014 12:31:21
Message-Id: 22299.1400761872@ccs.covici.com
In Reply to: Re: [gentoo-user] systemd seems to have broken logwatch by "J. Roeleveld"
1 J. Roeleveld <joost@××××××××.org> wrote:
2
3 > On Thursday, May 22, 2014 04:54:45 AM covici@××××××××××.com wrote:
4 > > Hi. I am having a strange problem running under systemd since Monday.
5 > > I use logwatch to get nice summaries of things going on in the system,
6 > > it gives me once a day summaries of such things. When running under
7 > > openrc, I used to get a summary of sshd activity, so I could see the
8 > > failed logins and the users that actually logged in via ssh. I was
9 > > using the sysklogd package and am still using it, although I had to
10 > > listen on a different socket. But now the sshd entries are totally gone
11 > > and I wonder how to get them back? For instance, I am no longer
12 > > getting the accepted public key messages anywhere.
13 > >
14 > > Thanks in advance for any suggestions.
15 >
16 > Did you configure logwatch to read from systemd (not sure if this is possible)
17 > or systemd to write the logs to sysklogd?
18 >
19 > Systemd uses it's own binary format for the logging by default.
20 I have sysklogd and friends listen on the journal socket rather on the
21 original socket which systemd has taken over. Strange but someone told
22 me that they were getting those messages with syslogng (name may be not
23 correct), but it still does not make sense to me.
24
25 --
26 Your life is like a penny. You're going to lose it. The question is:
27 How do
28 you spend it?
29
30 John Covici
31 covici@××××××××××.com

Replies

Subject Author
Re: [gentoo-user] systemd seems to have broken logwatch "J. Roeleveld" <joost@××××××××.org>