Bug 67947 - logrotate samba doesn't work right when using log files log.%m in smb.conf
Summary: logrotate samba doesn't work right when using log files log.%m in smb.conf
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: logrotate (Show other bugs)
(Show other bugs)
Version: 7.3
Hardware: i686 Linux
medium
medium
Target Milestone: ---
Assignee: Elliot Lee
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-04 17:27 UTC by Nicolas Bock
Modified: 2007-04-18 16:43 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-07-04 17:27:49 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 Nicolas Bock 2002-07-04 17:27:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020605

Description of problem:
The redhat default for log files in smb.conf is %m.log, for which logrotate
works great. When however this is changed to log.%m, logrotate fails to work
properly. The entry /var/log/samba/log.* in /etc/logroate.d/samba causes the
rotated log files to be rotated again, resulting in an infinite loop of
rotation. The file log.smbd for example will first be rotated to log.smbd.1.gz
and then to log.smbd.1.gz.1.gz and so forth.

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


How reproducible:
Always

Steps to Reproduce:
1.Change smb.conf log file setting to log.%m
2.Change in /etc/logrotate.d/samba /var/log/samba/log.*

	

Additional info:

Now you might say that one simply shouldn't change smb.conf's default to log.%m,
and I have to admit that I don't know how many people would do this, this might
therefore not be all too bad. I still think though that this is kind of an
interesting behavior.


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