From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id E35201381FA for ; Thu, 22 May 2014 09:17:01 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DB6CAE0A43; Thu, 22 May 2014 09:16:56 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id C528AE09F9 for ; Thu, 22 May 2014 09:16:55 +0000 (UTC) Received: from digimed.co.uk (shooty.digimed.co.uk [192.168.1.8]) by mail.digimed.co.uk (Postfix) with ESMTPA id 0B42D21E9E for ; Thu, 22 May 2014 10:16:55 +0100 (BST) Date: Thu, 22 May 2014 10:16:48 +0100 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] systemd seems to have broken logwatch Message-ID: <20140522101648.2587f6fb@digimed.co.uk> In-Reply-To: <18055.1400748885@ccs.covici.com> References: <18055.1400748885@ccs.covici.com> Organization: Digital Media Production X-Mailer: Claws Mail 3.9.3-212-ged5f07 (GTK+ 2.24.23; x86_64-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/JsZ=MJd0iy6RNzTILOcGud0"; protocol="application/pgp-signature" X-Archives-Salt: bdde65f2-c7e5-473d-a6f1-ac26f0f7083f X-Archives-Hash: c2545777800cc8efed9dfe92bb5f3aca --Sig_/JsZ=MJd0iy6RNzTILOcGud0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 22 May 2014 04:54:45 -0400, covici@ccs.covici.com wrote: > Hi. I am having a strange problem running under systemd since Monday. > I use logwatch to get nice summaries of things going on in the system, > it gives me once a day summaries of such things. When running under > openrc, I used to get a summary of sshd activity, so I could see the > failed logins and the users that actually logged in via ssh. I was > using the sysklogd package and am still using it, although I had to > listen on a different socket. But now the sshd entries are totally gone > and I wonder how to get them back? For instance, I am no longer > getting the accepted public key messages anywhere. I use syslog-ng with systemd and logcheck still show reports for sshd, so this may be specific to sysklogd. --=20 Neil Bothwick Electricians DO IT until it Hz... --Sig_/JsZ=MJd0iy6RNzTILOcGud0 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlN9wIAACgkQum4al0N1GQNYlgCg16wJkpHtbo/brIyqxoZ4uXwM Ch8AoNu/1sTSB+viFIiNrl7OnBWXmMJS =1OSg -----END PGP SIGNATURE----- --Sig_/JsZ=MJd0iy6RNzTILOcGud0--