Bug 755060 - Tor has a broken logrotate configuration
Summary: Tor has a broken logrotate configuration
Keywords:
Status: CLOSED DUPLICATE of bug 751525
Alias: None
Product: Fedora
Classification: Fedora
Component: tor
Version: 16
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Enrico Scholz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-18 17:14 UTC by Benjamin Lewis
Modified: 2011-11-29 15:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-29 15:02:17 UTC
Type: ---


Attachments (Terms of Use)
tor logrotate.d patch (381 bytes, patch)
2011-11-18 17:14 UTC, Benjamin Lewis
no flags Details | Diff

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 ***


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