RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1295467 - CR-LF-terminated lines break output formatting
Summary: CR-LF-terminated lines break output formatting
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: logwatch
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-04 15:37 UTC by Martin Frodl
Modified: 2016-04-28 11:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1295744 (view as bug list)
Environment:
Last Closed: 2016-04-28 11:14:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Martin Frodl 2016-01-04 15:37:10 UTC 
Description of problem:

When a log file processed by logwatch contains lines terminated with <CR><LF>,
<CR> is treated as a regular character rather than a part of the line break.
This has two unpleasant consequences:

(1) The log message may no longer match the specified pattern, making the line
    an unmatched entry. This may or may not be the expected behaviour.

(2) When printing a <CR><LF>-terminated entry, be it matched or unmatched, the
    carriage return is interpreted literally which breaks the output
    formatting.

Consider the following example, paying special attention to the **Unmatched
Entries** section in logwatch output:

# file /var/log/maillog
/var/log/maillog: ASCII text, with CRLF line terminators

# cat /var/log/maillog
Sep 24 04:17:27 mail1 sm-mta[14263]: k808NQxv028473: <wyman>... User unknown
Sep 24 04:19:01 mail1 sm-mta[12654]: k8O8F027026507: <cotter>... User unknown
Sep 24 04:25:33 mail1 sm-mta[14462]: k8O8VWJc037652: <helman>... User unknown

# logwatch --print --service sendmail --range all

 ################### Logwatch 7.3.6 (05/19/07) ####################
        Processing Initiated: Mon Jan  4 10:29:17 2016
        Date Range Processed: all
      Detail Level of Output: 0
              Type of Output: unformatted
           Logfiles for Host: qeos-32.lab.eng.rdu2.redhat.com
  ##################################################################

 --------------------- sendmail Begin (detail=3) ------------------------

 **Unmatched Entries**
: 1 Time(s)@tallhart.com>... User unknown
: 1 Time(s)manderly.com>... User unknown
: 1 Time(s) pyke.com>... User unknown
 ---------------------- sendmail End -------------------------


 ###################### Logwatch End #########################


Version-Release number of selected component (if applicable):
logwatch-7.3.6-52.el6.noarch
Note You need to log in before you can comment on or make changes to this bug.