Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Linux OS.: Technical questions -- Ignore unavailable to you. Want to Upgrade?

To: Thomas A Watson who wrote (318)	9/17/2002 8:28:19 PM
From: Thomas A Watson	Respond to of 484

ftp server how, redhat 7.3 Acutally with 7.2 and again with 7.3 the local ftp server deamon did not install and I had no local ftp server on my redhat 7.3 systems. With rsh, rlogin... etc working it's not a big deal as rcp will work. But I decided to figure why I could not ftp. First the deamon package needed to be installed is. wu-ftpd-2.6.2-5 To determine if it is installed. rpm -qa \|grep ftp gets a list of all installed ftp packages also one can look for /etc/xinetd.d/wu-ftpd if wu-ftpd is not installed get rpm wu-ftpd-2.6.2-5.i386.rpm rpm -U wu-ftpd-2.6.2-5.i386.rpm this also creates /etc/xinetd.d/wu-ftpd contents of # default: on # description: The wu-ftpd FTP server serves FTP connections. It uses # normal, unencrypted usernames and passwords for authentication. service ftp { socket_type = stream wait = no user = root server = /usr/sbin/in.ftpd server_args = -l -a log_on_success += DURATION nice = 10 disable = no } NOTE: last line should be edited to disable = no after that serviceconf can be run as root and xinetd can be restarted. The clue to this solution was found after much google searching and then I looked at redhat in the listman.redhat.com listman.redhat.com

To: Thomas A Watson who wrote (318)	3/22/2008 4:29:52 PM
From: Thomas A Watson	Respond to of 484

rsh rlogin install on Fedora Core 8 This works on my systems currently running redhat 7.3 Fedora Core 3 and Fedora Core 8. I did a google and did not find any fruitful info, so I called upon my memory, made guesses and tested until I got to work. FC8 package does not contain the following packages. the rev level is what I used. xinetd-2.3.14-9.fc6.i386.rpm FC8 uses inetd default rsh-server-0.17-44.fc8.i386.rpm from a google I found this site and the got the rpms above. fr.rpmfind.net I installed rpm -U dahdahdah.rpm It's what I always remember and it always has worked for me. rpm -qa gives list of currently installed rpm packages. After install I used sysadmin tool to start xinetd and rsh server. Also had to start rsh rlogin rexec sevices poked around the sysadmin tool and finally found them. If you also wish no password login among trusted hosts you also must do the following... <p>No Passwords is the whole Point. edit /etc/hosts.allow I added # # hosts.allow This file contains access rules which are used to # allow or deny connections to network services that # either use the tcp_wrappers library or that have been # started through a tcp_wrappers-enabled xinetd. # # See 'man 5 hosts_options' and 'man 5 hosts_access' # for information on rule syntax. # See 'man tcpd' for information on tcp_wrappers # ALL: 192.168.1.2 ALL: 192.168.1.3 ALL: 192.168.1.4 ALL: 192.168.1.5 ALL: 192.168.1.6 ALL: 192.168.1.7 ALL: 192.168.1.8 ALL: 192.168.1.9 ALL: 192.168.1.155 ALL: 192.168.1.20 ALL: 192.168.1.21 ALL: 192.168.1.100 ALL: 192.168.1.101 ALL: 192.168.1.102 Then create in the users home directory a .rhosts [watson@right ~]$ cat .rhosts obtuse twent acute right obleak square half 4t5 1at 9d angle tv obtuse.watman.com twent.watman.com acute.watman.com right.watman.com obleak.watman.com square.watman.com half.watman.com 4t5.watman.com 1at.watman.com 9d.watman.com angle.watman.com tv.watman.com I think you only need whatever the HOST variable is set to on the target machine for the no password to really work. [ 253 ] > env \|grep -i host will display the HOST variable. I also did a chmod to 644 on .rhosts did not check to see if that matters. It may be some crossed memory of .netrc permission rule. I think I've covered it all....