Author: Robert Hyatt
Date: 08:27:11 05/16/01
Go up one level in this thread
On May 16, 2001 at 10:54:48, Andrew Williams wrote: >On May 15, 2001 at 20:48:11, James Swafford wrote: > >>On May 15, 2001 at 18:33:44, Andrew Williams wrote: >> >>>Hi James, >>> >>>I did something like this last Summer. In my case, I was using two Linux >>>machines, but the principle was the same. I found that I could only make >>>it work if the executables were in my home directory I didn't really have >>>time to find out why. Here's the essence of my shell script: >>> >>># script starts here >>>setenv CHESSDIR ~/testmatch >>> >>>~/bin/xboard -fcp "./ewith xboard" -scp "./gwithout xboard" -sh 99.99.99.99 \ >>> -size Middling -animateMoving False -mg 20 -sgf testmatch.pgn \ >>> -tc 5 -inc 2 -showCoords True \ >>> -popupExitMessage False >>> >>># script ends here >>> >>>Notice that ewith and gwithout were both in my home directory on Linux >>>machines. Notice also that I had to specify the host for the second program >>>(-sh) with the ip number, rather than the domain name. >> >>The Winboard documentation does have something to say about why your >>executables had to be in the home directory; I think it said you had >>to issue a cd command within the fd parameter. > >Well, thank you for solving *my* problem :-). What was the message >about permission problems you got when you tried rsh from the command >line? > >Andrew > > There are two things you need to make rsh work reliably: 1. on the remote machine you need a .rhost file with the name of the local machine in it. 2. you probably want to add the local host to the remote machine's /etc/host.equiv file as well. Then rsh/rlogin/rcp/etc should all work perfectly from the local machine to the remote machine. > >> >>Anyway, I think I'm a little closer to figuring this thing out, but >>I'm still having some problems with remote shelling anything on the >>Linux box from my Windows box. >> >>I downloaded a nifty utility called rsh from http://www.csa.ru/~il/rsh/. >>When I ran the utility from the command line, it indicated there were >>some permission problems. I never did see the rshd daemon run on the >>Linux machine - my understanding is that inetd should start the daemon >>when it's needed. That led me to examine the /etc/inetd.conf file, >>which contained the following: >> >># >># Shell, login, exec, comsat and talk are BSD protocols. >># >>shell stream tcp nowait root /usr/sbin/tcpd in.rshd >>login stream tcp nowait root /usr/sbin/tcpd in.rlogind >>#exec stream tcp nowait root /usr/sbin/tcpd in.rexecd >>#comsat dgram udp wait root /usr/sbin/tcpd in.comsat >>talk dgram udp wait nobody.tty /usr/sbin/tcpd in.talkd >>ntalk dgram udp wait nobody.tty /usr/sbin/tcpd in.ntalkd >>#dtalk stream tcp wait nobody.tty /usr/sbin/tcpd in.dtalkd >> >>I could be way off in left field, but it seems my problem isn't so >>much with _Winboard_, but with remote shelling in general. I'm afraid >>my limited experience with rsh isn't helping matters much. >> >>So, what simple test can I perform to try remote shelling? Does >>anybody have any links or pointers where I could read further? Anybody >>out there successfully remote shelled an engine on a Linux/Unix machine >>from a Windows machine? >> >>Advice greatly appreciated! I could run the program on this Windows >>machine, but it's much slower, and I really wanna get this to work. >> >>Thanks, >> >>-- >>James
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.