View Single Post
  #22  
Old 22nd March 2006, 02:40
latcarf latcarf is offline
Senior Member
 
Join Date: Jul 2005
Posts: 215
Thanks: 0
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by falko
Please put

Code:
local_umask=022
chroot_local_user=YES
into /etc/vsftpd.conf and restart vsftpd:
Code:
/etc/init./vsftpd restart
Please use the vsftpd init script in /etc/init.d to start/stop/restart vsftpd.
I changed the config file as you asked. The problem is I do not have a /etc/init./vsftpd file! A search for "vsftpd" got this
Code:
file:///etc/logrotate.d/vsftpd
file:///etc/pam.d/vsftpd
file:///etc/xinetd.d/vsftpd
file:///usr/sbin/vsftpd Indicates this is an Executable file
file:///usr/share/doc/packages/vsftpd
The intersting thing is that in file:///usr/share/doc/packages/vsftpd I read that I do not need inted or xinted. There are various configs available so I selected the one I need (standalone), followed the instructions and it worked, almost. I still could not do an anonymous upload so I went back and changed the Write lines from NO to YES.
The second issue came in then, Stop, Start, and Restart are not being recognized by Konsole. This is the responses I get
Code:
server1:~ # vsftpd stop
500 OOPS: vsftpd: cannot open config file:stop
server1:~ # vsftpd start
500 OOPS: vsftpd: cannot open config file:start
server1:~ # vsftpd restart
500 OOPS: vsftpd: cannot open config file:restart
server1:~ # vsftpd &
[1] 6542
500 OOPS: could not bind listening IPv4 socket
server1:~ #
All the documentation I find points to using "&" to start the service but I am beginning to think this is not used to Stop or Restart the service. I am beginning to think that "&" is for start only and I keep getting
Code:
[B]500 OOPS: could not bind listening IPv4 socket
because it is already running and I need to restart it for changes to take effect. I have Googled myself silly trying to find "&" and what stop and restart might be but I am having no luck
Reply With Quote