Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
i have a problem where on re-boot of our RH9 server the ProFTPD server is unable to start because xinetd hogs port 21, i have to stop xinetd - start FTP - then restart xinetd, any ideas as to why this might be happening?
Look in the /etc/xinetd.conf file for a line like this
If you have that line then look in the /etc/xinetd.d directory for any ftp file like wu-ftpd. If you have one then edit the file and disable the service. disable = yes
the cmd chkconf --list proftpd returns a no such file or directory error, chkconf --list on its own shows a big list of services but alas, proftpd is not one of them. Service proftpd returns a unrecognized service error, and to start the service i have to use Webmin. i also noticed that the only running processes that webmin is reporting is the proftpd processID and that its parent process is init. i did edit the xinetd.conf file but once again proftpd wouldn't start on re-boot so Ive reversed those changes and are back at square one. i noticed in Webmin that the proftpd server is set to start automatically using the Internet services module but when looking at the setup within that module can see that it is being palmed off to in.proftpd [in. I assume stands for init] as opposed to the option of having the service handled by xinetd, i will try changing this option unless you have any further suggestions?
hi /bin/bash, soz i've taken a few days to reply - things went crazy round here.
the ps -ax cmd shows that proftpd is not started after a re-boot.
netstat -ta shows local address *:ftp & nothing else that i can see listening on port 21, i tried the switch -antp & that shows xinetd listening on port 21 & on port 110 - unfortunately im not sure what all this means...?
Apr 1 19:02:25 sun proftpd: sun.xxxx.be - Failed binding to 0.0.0.0, port 21: Address already in use
Apr 1 19:02:25 sun proftpd: sun.xxxx.be - Check the ServerType directive to ensure you are configured correctly.
The problem was due to the fact that inetd was listening of port 21, which is precisely the port use by proftp.
Here is the content of my the proftpd.conf file:
[root@sun etc]# more /etc/proftpd.conf
# This is a basic ProFTPD configuration file (rename it to
# 'proftpd.conf' for actual use. It establishes a single server
# and a single anonymous login. It assumes that you have a user/group
# "nobody" and "ftp" for normal operation and anon.
ServerName "ProFTPD Default Installation"
# Allow FTP resuming.
# Remember to set to off if you have an incoming ftp for upload.
# Port 21 is the standard FTP port.
# Umask 022 is a good standard umask to prevent new dirs and files
# from being group and world writable.
# To prevent DoS attacks, set the maximum number of child processes
# to 30. If you need to allow more than 30 concurrent connections
# at once, simply increase this value. Note that this ONLY works
# in standalone mode, in inetd mode you should use an inetd server
# that allows you to limit maximum number of processes per service
# (such as xinetd).
# Set the user and group under which the server will run.
# To cause every FTP user to be "jailed" (chrooted) into their home
# directory, uncomment this line.
# Normally, we want files to be overwriteable.
# Needed for NIS.
# Default root can be used to put users in a chroot environment.
# As an example if you have a user foo and you want to put foo in /home/foo
# chroot environment you would do this:
# DefaultRoot /home/foo foo
My problem came from Servertype which was Standalone and which should have been inetd (as I use inetd and do not run proftpd as daemon)
Finally, my proftpd-xinetd file looks like this:
[root@sun etc]# more /etc/xinetd.d/proftpd-xinetd
# default: off
# description: proftpd server, xinetd version. \
# Don't run the standalone version if you run \
disable = no
socket_type = stream
wait = no
user = root
server = /usr/sbin/in.ftpd
log_on_success += DURATION USERID
log_on_failure += USERID
nice = 10
I have also deleted the FTP file from that directory.
Now you just have to adapt proftpd.conf file in order to grant / deny access to users.
I have spent evenings during 2 weeks trying to solve this. Hope this will also work fine for you with those indications.
cheers for the post Vincent, my /etc/proftpd.conf file has Servertype as standalone so i changed it to xinetd but this made no difference. what i dont have is a /etc/xinetd.d/proftpd-xinetd file - do i need to create one? & why wouldnt there already be one?