Bug 156089 - Output in unmatched entries section of SSHD runs together as one long line
Output in unmatched entries section of SSHD runs together as one long line
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: logwatch (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ivana Varekova
Depends On:
  Show dependency treegraph
Reported: 2005-04-27 09:54 EDT by Martin Gottlieb
Modified: 2007-11-30 17:06 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-29 06:38:57 EDT
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 Martin Gottlieb 2005-04-27 09:54:36 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Description of problem:
Need newline between entries - change line 243 in sshd script 


print @OtherList;


print join( "\n", @OtherList );

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

How reproducible:

Steps to Reproduce:
1. Run logwatch script
2. Review results

Actual Results:  Entries in "unmatched entries" sub-section of the SSHD service section
are run together as one long line and are difficult to read.

Expected Results:  Each entry should appear on a separate line.

Additional info:
Comment 1 John Dalbec 2005-05-02 09:01:50 EDT
--- sshd        Mon May  2 08:52:46 2005
+++ /etc/log.d/scripts/services/sshd    Mon May  2 08:53:02 2005
@@ -240,7 +240,7 @@
    if ($#OtherList >= 0) {
       print "\n**Unmatched Entries**\n";
-      print @OtherList;
+      print join "\n", @OtherList;
    print "\n\n ---------------------- SSHD End ------------------------- \n\n";
Comment 2 Ivana Varekova 2005-08-29 06:38:57 EDT
This does not meet the requirements for RHEL 2.1, which is currently in
maintenance mode; as such, this won't be fixed for 2.1.

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