Bug 91408 - logrotate should handle glob failures gracefully
logrotate should handle glob failures gracefully
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: logrotate (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Elliot Lee
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-05-22 09:00 EDT by David N. Blank-Edelman
Modified: 2015-01-07 19:05 EST (History)
1 user (show)

See Also:
Fixed In Version: 3.6.9
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-07-09 15:14:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David N. Blank-Edelman 2003-05-22 09:00:13 EDT
Although logrotate is happy to continue with the logging process if a file 
doesn't exist (given "missingok"), it will die mid-job if there is a globbing 
error even if missingok is set. For instance, if you ask to 
rotate /priv/log/somedir/*.log and the somedir directory doesn't exist, 
logrotate will exit with an error even if "missingok" is set for that glob'd 
file.

Possible ideas for fixes:

1) have logrotate respect missingok when glob errors are encountered
2) add another primative (e.g. missingdirok)
Comment 1 Elliot Lee 2003-07-08 15:59:48 EDT
Patches anyone?

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