Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 113853 - Sendmail and samba3 issues
Sendmail and samba3 issues
Status: CLOSED DUPLICATE of bug 113802
Product: Fedora
Classification: Fedora
Component: logwatch (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Elliot Lee
Depends On:
  Show dependency treegraph
Reported: 2004-01-19 10:38 EST by Petr Krištof
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:00:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Petr Krištof 2004-01-19 10:38:13 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)

Description of problem:
Logwatch version used in FC-1 is totaly outdated.
It doesnt catch sendmail or samba logfiles.

For example it reports all sendmail SSL connection, on high traffic
hosts it is several thousands lines daily.

STARTTLS=client, relay=[], version=TLSv1/SSLv3, verify=NO,
cipher=DHE-RSA-AES256-SHA, bits=256/256: 10000 Time(s)
STARTTLS=server, relay=localhost.localdomain [],
version=TLSv1/SSLv3, verify=NO, cipher=DHE-RSA-AES256-SHA,
bits=256/256: 10000 Time(s)

The same situation comes with samba. All netlogon connection are
reported. All share mounts/unmounts are reported.

The logwatch package must be updated to most up to date version.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Additional info:
Comment 1 Peter van Egdom 2004-01-28 04:51:36 EST
See Bugzilla Bug 113802
Comment 2 Petr Krištof 2004-01-28 05:08:13 EST
Yes. Update to Logwatch 5.0 will fix it.

*** This bug has been marked as a duplicate of 113802 ***
Comment 3 Red Hat Bugzilla 2006-02-21 14:00:50 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.