[Logwatch] No more SSH logs

Michel Esber michel@us.automatos.com
Tue, 16 Jul 2002 10:40:59 -0800


This is a multi-part message in MIME format.

------=_NextPart_000_018D_01C22CB5.45EFA070
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

    I have a RedHat 7.3 installation running on one of my machines,
and LogWatch used to work fine. Logs from all daemons were shown
in the email that I received.

    Because of security issues, I had to upgrade my OpenSSH=20
packages (to 3.4p1). Since then, I do not receive any SSH log =
information.=20
The others still work fine, but not SSH.

uname -a
Linux proliant 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown

[root@proliant cron.daily]# rpm -qa | grep logwatch
logwatch-3.3-2

Any ideas ?

Best,
=20
Michel Esber
michel@us.automatos.com

Microsoft Certified Professional

Office: (408) 725-7141
Mobile: (408) 316-9288
=20
Problems with expensive Capacity Planning solutions? Try =
www.automatos.com
 
------=_NextPart_000_018D_01C22CB5.45EFA070
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4916.2300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; I have a RedHat 7.3 =
installation=20
running on one of my machines,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and LogWatch used to work fine. Logs =
from all=20
daemons were shown</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in the email that I =
received.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; Because of security =
issues, I=20
had to upgrade my OpenSSH </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>packages (to 3.4p1). Since then, I do =
not receive=20
any SSH log information. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The others still work fine, but not=20
SSH.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>uname -a</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Linux proliant 2.4.18-3 #1 Thu Apr 18 =
07:37:53 EDT=20
2002 i686 unknown<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>[root@proliant cron.daily]# rpm -qa | =
grep=20
logwatch<BR>logwatch-3.3-2<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Any ideas ?</FONT><FONT face=3DArial=20
size=3D2></DIV></FONT><FONT face=3DArial size=3D2>
<DIV><BR>Best,<BR>&nbsp;<BR>Michel Esber<BR><A=20
href=3D"mailto:michel@us.automatos.com">michel@us.automatos.com</A></DIV>=

<DIV>&nbsp;</DIV>
<DIV>Microsoft Certified Professional</DIV>
<DIV>&nbsp;</DIV>
<DIV>Office: (408) 725-7141<BR>Mobile: (408) =
316-9288<BR>&nbsp;<BR>Problems with=20
expensive Capacity Planning solutions? Try <A=20
href=3D"http://www.automatos.com">www.automatos.com</A><BR>&nbsp;</FONT><=
/DIV></BODY></HTML>

------=_NextPart_000_018D_01C22CB5.45EFA070--