Bug 55824 - samba-2.0.10-0.521 logrotate script uses unrecognized "missingok" and "sharedscripts"
Summary: samba-2.0.10-0.521 logrotate script uses unrecognized "missingok" and "shared...
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: samba (Show other bugs)
(Show other bugs)
Version: 5.2
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-07 09:28 UTC by Davide Bolcioni
Modified: 2007-04-18 16:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-11-07 09:28:16 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Davide Bolcioni 2001-11-07 09:28:11 UTC
Description of Problem:
samba-2.0.10-0.521 logrotate script uses unrecognized "missingok" 
and "sharedscripts", which results in an error message being
mailed daily to the administrator

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

How Reproducible:
Daily on a 5.2 machine (logrotate is too old and no upgrade
was ever issued).

Steps to Reproduce:
1. upgrade to samba-2.0.10-0.521
2. 
3. 

Actual Results:
Daily error message

Expected Results:
No error message

Additional Information:
This is a recurring problem with 5.2 updates, see for example
bug #4744; easily fixed by the local admin, just comment out the
offending stuff, but the use of "sharedscripts" suggests that
whoever put together the logrotate script might expect it to do
something which on a RedHat 5.2 would not be done. Maybe an
upgrade to logrotate, like the RPM 4.x upgrade, would fix
such annoyances once for all.

Comment 1 Trond Eivind Glomsrxd 2001-11-07 16:38:13 UTC
RHL 5.2 is no longer supported (the support time is 3 years from release for
end-of-series releases), newer releases don't have this problem.


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