Bug 129941 - vsftpd logs do not rotate by default.
Summary: vsftpd logs do not rotate by default.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: vsftpd
Version: 3.0
Hardware: i686
OS: Linux
medium
low
Target Milestone: ---
Assignee: Martin Nagy
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-14 22:50 UTC by Chris Carr
Modified: 2016-07-26 23:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-01 12:38:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Chris Carr 2004-08-14 22:50:58 UTC
Description of problem:
Default RPM install contains file /etc/logrotate.d/vsftpd.log which
contains:
/var/log/vsftpd.log {
    # ftpd doesn't handle SIGHUP properly
    nocompress
    missingok
}

However, the default behavior for the daemon is to write to
/var/log/xferlog -- not to /var/log/vsftpd.log. No logrotate config
file is provided for /var/log/xferlog.

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

How reproducible:
Install Red Hat Enterprise Linux 3.0, selecting the FTP Server package
in the process. Start the vsftpd daemon. Transfer a few files. Observe
that transfer activity is logged to /var/log/xferlog. Wait a week.
Observe that /var/log/xferlog has not been rotated.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
logrotate config contains directive to rotate /var/log/vsftpd.log.
/var/log/xferlog grows indefinitely without being rotated.

Expected results:
logrotate config should contain directive to rotate /var/log/xferlog;
or daemon should log to /var/log/vsftpd.log. I prefer the former behavior.

Additional info:

Comment 1 Radek Vokál 2004-08-23 08:03:20 UTC
Logging was fixed in vsftpd-2.0.1.

Comment 2 Martin Nagy 2008-02-01 12:38:11 UTC
I'm sorry but for RHEL-3 we currently only fix regressions and mission critical
bug. Hence closing as WONTFIX.


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