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 18754 - logrotate does not handle log files with spaces in the file name
logrotate does not handle log files with spaces in the file name
Product: Red Hat Linux
Classification: Retired
Component: logrotate (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Erik Troan
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2000-10-09 18:48 EDT by Need Real Name
Modified: 2007-04-18 12:29 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-10-10 10:31:46 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 Need Real Name 2000-10-09 18:48:42 EDT
Log files with spaces in their file names makes logrotate unable to parse
its state file.  The error report sent from cron daemon says

   error: bad line 34 in state file /var/lib/logrotate.status

Line 34 is 

   /var/log/samba/log.chief wiggum 2000-9-2

The file "/var/log/samba/log.chief wiggum" exists with normal permissions.

Logrotate does not rotate any log files when it fails to read its state

My guess is that logrotate uses space as field separator in the state file
and that it has no way of telling when a space is part of a file name or a
field separator.

Version:  logrotate-3.3.2-1 on redhat 6.2.  Other versions or platforms
Comment 1 Erik Troan 2000-10-10 10:31:42 EDT
Fixed in the logrotate included with 7.0
Comment 2 Bishop Clark 2001-01-30 09:10:42 EST
The careful observer will note that the original bug was reported against 6.2 .  Will the 7.0 fix released also work on 6.2, or is a backport to address the 
original report in the works?

Comment 3 Erik Troan 2001-01-30 11:24:49 EST
The sources will rebuild fine, the binary package won't work.

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