Bug 755060

Summary: Tor has a broken logrotate configuration
Product: [Fedora] Fedora Reporter: Benjamin Lewis <ben.lewis>
Component: torAssignee: Enrico Scholz <rh-bugzilla>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: liblit, lmacken, rh-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-29 15:02:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
tor logrotate.d patch none

Description Benjamin Lewis 2011-11-18 17:14:16 UTC
Created attachment 534455 [details]
tor logrotate.d patch

Description of problem:
Tor's logrotate configuratuon causes logrotate to complain, and hence generates needless (ana)cron e-mails. Also, this results in no logs being rotated, due to the error:

"/etc/cron.daily/logrotate:

error: skipping "/var/log/tor/*.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation."

Version-Release number of selected component (if applicable):
tor-0.2.2.34-1600.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install tor
2. /usr/sbin/logrotate /etc/logrotate.conf (essentially what cron does)
  
Actual results:
An error - and hence cron e-mails

Expected results:
Logs get rotated

Additional info:
Trivial one line patch is attached, unsure if this is the correct fix, however!

Comment 1 Ben Liblit 2011-11-23 16:35:39 UTC
This is a duplicate of bug #751525, but it seems I don't have permission to mark it as such officially.

Comment 2 Benjamin Lewis 2011-11-29 15:02:17 UTC

*** This bug has been marked as a duplicate of bug 751525 ***