Bug 136047 - vsftpd doesn't start
Summary: vsftpd doesn't start
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: vsftpd
Version: rawhide
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Radek Vokál
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-17 05:55 UTC by Mike
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-10-18 07:18:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mike 2004-10-17 05:55:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20041012

Description of problem:
The /etc/init.d/startup file specifies that command to start up vsftpd
is "/usr/sbin/vsftpd vsftpd &" according to the way the pathname is
parsed in the script.  However, the filename in /etc/vsftpd is named
"vsftpd.conf" not "vsftpd" and it therefore doesn't start properly
when passed as an argument in the script.

Code snippet from from /etc/init.d/vsftpd

        if [ -d /etc/vsftpd ] ; then
                for i in `ls /etc/vsftpd/*.conf`; do
                        site=`basename $i .conf`
                        echo -n $"Starting $prog for $site: "
                        /usr/sbin/vsftpd $i &
                        RETVAL=$?
                        [ $RETVAL -eq 0 ] && {
                           touch /var/lock/subsys/$prog
                           success $"$prog $site"
                        }
                        echo
                done


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

How reproducible:
Always

Steps to Reproduce:
1./etc/init.d/vsftpd start
2.ps aux | grep vsftpd
3.
    

Actual Results:  no vsftpd process has started

Expected Results:  a vsftpd process

Additional info:

Comment 1 Radek Vokál 2004-10-18 07:18:24 UTC
This script is correct and uses vsftpd.conf file. I don't see any
problem here.


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