randy@umn-cs.cs.umn.edu (Randy Orrison) (08/06/88)
Questions for comp.unix.questions:
Is there an RFC for rcp?
Is there a more recent RFC for FTP than 959?
How does a person keep track of new RFCs?
Thanks!
-randy
--
Randy Orrison, Chemical Computer Thinking Battery -- randy@cctb.mn.org
randy@ux.acss.umn.edu {bungia, uunet!hi-csc, rutgers, sun}!umn-cs!randy
"You're only human, what can you do? It'll soon be over..."Leisner.Henr@xerox.com (Marty) (03/01/89)
Here's (hopefully a simple one) -- I want to rcp between two machines which support it. I have different accounts on both machines. I've looked at the documents on .rhosts files and I'm not sure what it's all about.. I have each machine with an .rhosts file in my home directory which looks like: host1 user1 host2 user2 No matter what I do (I'm playing with rsh and rcp) I get: Permission denied. I have no problem rcp'ing from each machine with NCSA telnet on ms/dos. (There's no password protection or security enabled with NCSA telent). Now how do I get these machines to talk rcp to each other? (FTP works with no problem -- but I want something a little more seamless). marty ARPA: leisner.henr@xerox.com GV: leisner.henr NS: martin leisner:wbst139:xerox UUCP: hplabs!arisia!leisner
gwyn@smoke.BRL.MIL (Doug Gwyn ) (03/01/89)
In article <18479@adm.BRL.MIL> Leisner.Henr@xerox.com (Marty) writes: >No matter what I do (I'm playing with rsh and rcp) I get: >Permission denied. First, "rlogin" to the remote system. Use the "who" command to see what the remote system thinks your host name really is. Then edit the remote .rhosts file to spell the host name EXACTLY that way.
jonathan@cs.keele.ac.uk (Jonathan Knight) (03/01/89)
From article <18479@adm.BRL.MIL>, by Leisner.Henr@xerox.com (Marty): > Here's (hopefully a simple one) -- > > I want to rcp between two machines which support it. > > I have different accounts on both machines. I have a similar situation. I put a .rhosts file in my home directory like this: For host1 I have: host2 username2 For host2 I have host1 username1 Then to rcp a file from host1 to host2 while logged into host1 rcp file host2.username2:file and to rcp from host2 to host1 while logged into host1 rcp host2.username2:file file Of course you should remember to remove the .rhosts files when you no longer need them :-). -- ______ JANET :jonathan@uk.ac.keele.cs Jonathan Knight, / BITNET:jonathan%cs.kl.ac.uk@ukacrl Department of Computer Science / _ __ other :jonathan@cs.keele.ac.uk University of Keele, Keele, (_/ (_) / / UUCP :...!ukc!kl-cs!jonathan Staffordshire. ST5 5BG. U.K.
pinkas@hobbit.intel.com (Israel Pinkas ~) (03/02/89)
In article <18479@adm.BRL.MIL> Leisner.Henr@xerox.com (Marty) writes: > Here's (hopefully a simple one) -- > > I want to rcp between two machines which support it. > > I have different accounts on both machines. > > I've looked at the documents on .rhosts files and I'm not sure what it's > all about.. I have each machine with an .rhosts file in my home directory > which looks like: > host1 user1 > host2 user2 > > No matter what I do (I'm playing with rsh and rcp) I get: > Permission denied. > > I have no problem rcp'ing from each machine with NCSA telnet on ms/dos. > (There's no password protection or security enabled with NCSA telent). Now > how do I get these machines to talk rcp to each other? > > (FTP works with no problem -- but I want something a little more seamless). The man pages for all the machines that I use (Ultrix & sunOS) state that you need to do something like: rcp mach.user:file localfile Rcp is similar to cp, in that you need to specify at leas two names on the command line. When there are more than two, the last must be a directory. Rcp also allows the -r flag, which does recursive copies. (The last file must be a directory.) Some version of rcp have other flags, but they are not universally supported. Rcp uses the following as a filespec: [remotemach[.remoteuser]:][filename] The filename is the name of a file specified on the appropriate machine. It may be either the name of a file, or a directory, as appropriate. It need not exist, if the conext allows that. (That is, the destination file need not exits. When remotemach (with the :) is not specified, the filename is taken to be on the local machine. When remoteuser is not specified, it defaults to the name of the current user. (Different implementations vary on whether real uuid or su'ed uid is used when su'ed.) If filename is nonexistent (only valid for destination), . is assumed (that is, the login directory for remoteuser. Filename must be present if remotemach is absent. That is, the following are valid: localfile remotemach:file remotemach.remoteuser:remotefile remotemach: # only for destination remotemach.remoteuser: # ditto Hope this helps. -Israel -- -------------------------------------- Disclaimer: The above are my personal opinions, and in no way represent the opinions of Intel Corporation. In no way should the above be taken to be a statement of Intel. UUCP: {amdcad,decwrl,hplabs,oliveb,pur-ee,qantel}!intelca!mipos3!cadev4!pinkas ARPA: pinkas%cadev4.intel.com@relay.cs.net CSNET: pinkas@cadev4.intel.com