Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Redhat Linux 7.0 Apache/1.3.27 PHP Version 4.3.1 server api Apache
Posts: 46
Rep:
inetd VS xinetd
I could really use some help from you guys.
I have searched and searched for a solution on the boards.
I've tried just about everything with no luck.
I'm trying to install proftpd on my new server using Redhat Linux 7.2
Everyone says to do this and that with the inetd file. I don't have an inetd file on my new server. I have that file on my old server and proftpd works fine.
I do have xinetd on my new server. Any experience this?
I'll be glad to supply additional information if needed.
Your help would greatly be appreciated. This is driving me insane.
xinetd is basically a newer version of inetd. I guess it's supposed to be more secure. Each of them are called "super daemons" because they can controll a whole bunch of other daemons in one package (I think that this ends up being part of their downside too ). You should use xinetd if you are going to use them.
Xinetd can be configured either with the file /etc/xinetd.conf, or with a directory having that name and a bunch of files inside of it. I use the single file option myself, but I think most people opt for the directory one.
then you add entries for each of the other servers that you want xinetd to controll, for example, here's my entry for sshd:
service ssh
{
socket_type = stream
protocol = tcp
wait = no
user = root
port = 22
server = /usr/sbin/sshd
server_args = -i
}
Now, If you wanted to use the /etc/xinetd.conf/ DIRECTORY option, you would have each of these sections in their own text file named "defaults" "<maybe service> ssh"
Distribution: Redhat Linux 7.0 Apache/1.3.27 PHP Version 4.3.1 server api Apache
Posts: 46
Original Poster
Rep:
Thanks for the help fellows.
I must be missing something.
Would someone mind looking at my server and seeing what I'm doing wrong? I can email you the info to get on the server.
I've tried alot of things posted on the boards and so far no luck.
Distribution: Redhat Linux 7.0 Apache/1.3.27 PHP Version 4.3.1 server api Apache
Posts: 46
Original Poster
Rep:
Here is the file.
Oct 20 04:02:03 www3 syslogd 1.4.1: restart.
Oct 20 12:17:16 www3 sshd(pam_unix)[17231]: session opened for user root by (uid=0)
Oct 20 12:22:03 www3 xinetd[21415]: Exiting...
Oct 20 12:22:03 www3 xinetd: xinetd shutdown succeeded
Oct 20 12:22:03 www3 xinetd[17600]: id not unique: ftp [line=12]
Oct 20 12:22:03 www3 xinetd[17600]: xinetd Version 2002.03.28 started with libwrap options compiled in.
Oct 20 12:22:03 www3 xinetd[17600]: Started working: 1 available service
Oct 20 12:22:06 www3 xinetd: xinetd startup succeeded
Oct 20 12:27:49 www3 xinetd[17600]: Exiting...
Oct 20 12:27:49 www3 xinetd: xinetd shutdown succeeded
Oct 20 12:27:49 www3 xinetd[18025]: id not unique: ftp [line=12]
Oct 20 12:27:49 www3 xinetd[18025]: xinetd Version 2002.03.28 started with libwrap options compiled in.
Oct 20 12:27:49 www3 xinetd[18025]: Started working: 1 available service
Oct 20 12:27:52 www3 xinetd: xinetd startup succeeded
Originally posted by dave4545 Here is the file.
Oct 20 04:02:03 www3 syslogd 1.4.1: restart.
Oct 20 12:17:16 www3 sshd(pam_unix)[17231]: session opened for user root by (uid=0)
Oct 20 12:22:03 www3 xinetd[21415]: Exiting...
Oct 20 12:22:03 www3 xinetd: xinetd shutdown succeeded
Oct 20 12:22:03 www3 xinetd[17600]: id not unique: ftp [line=12]
Distribution: Redhat Linux 7.0 Apache/1.3.27 PHP Version 4.3.1 server api Apache
Posts: 46
Original Poster
Rep:
I don't have a file named ftp under the
/etc/xinetd.d directory.
I have a file called proftpd under that directory.
The contents on that file are
service ftp
{
disable = no
flags = REUSE
socket_type = stream
instances = 150
wait = no
user = ftp
server = /usr/local/sbin/proftpd
log_on_success = HOST PID
log_on_failure = HOST RECORD
}
Distribution: Redhat Linux 7.0 Apache/1.3.27 PHP Version 4.3.1 server api Apache
Posts: 46
Original Poster
Rep:
I changed user=ftp
user=root
I nolonger get that error message.
When I try to logon using my WS_ftppro program I get a connection refused.
I checked my proftpd.log and messages log and nothing shows that I tried to ftp to the site.
Distribution: Redhat Linux 7.0 Apache/1.3.27 PHP Version 4.3.1 server api Apache
Posts: 46
Original Poster
Rep:
Yeah. I followed the instructions that were given on the proftpd site.
Once that didn't work I started trying all kinds of different things that didn't seem to work.
Now that I've done all of that it would probably be best for me to start over.
Look for someone who can assist and find out why this easily installed software was not so easy on my server.
cp proftpd-*.bz2 /usr/src
cd /usr/src
tar xvfj proftpd-*.bz2
cd proftpd-*
./configure \
--prefix=/usr/server \
--sysconfdir=/etc
make
make install
cd /usr/src
rm -r proftpd*
And /etc/xinetd.d/ftp
Code:
service ftp
{
disable = no
flags = REUSE
socket_type = stream
instances = 150
wait = no
user = root
server = /usr/server/sbin/proftpd
log_on_success = HOST PID
log_on_failure = HOST RECORD
}
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.