home *** CD-ROM | disk | FTP | other *** search
- X-Gateway-Source-Info: INTERNET
- Path: sparky!uunet!spool.mu.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!network.ucsd.edu!mvb.saic.com!tgv.com!info-multinet
- Date: 07 SEP 92 07:13:42 GMT
- Newsgroups: vmsnet.networks.tcp-ip.multinet
- X-Return-path: <info-multinet-relay@TGV.COM>
- X-RFC822-From: adelman (Kenneth Adelman) @ TGV.COM
- From: adelman@TGV.COM
- Subject: Re: RCP and LOGIN.COM problem
- Organization: The INFO-MULTINET Community
- Message-ID: <2460313607SEP92071342@TGV.COM>
- Nntp-Posting-Host: Mvb.Saic.Com
- Lines: 22
-
- > This may be a FAQ but ...
-
- > When the MultiNet 'rcp' server calls any Unix 'rcp' client, everything works.
- > However, the Unix 'rcp' server bombs out when talking to MultiNet 'rcp' client
- > because the first line of the user's login.com is always sent back to the
- > server.
-
- > unix$ rcp junk.txt vms.node
- > $! first line from login.com even if it is '$ set noverify'
-
- > vms$ dir junk.txt
- > %DIRECT-W-NOFILES, no files found
-
- > vms$ rcp unix::"junk.txt" []/log
- > %RCP-I-COPIED, UNIX::junk.txt copied to VMS:[DIR]JUNK.TXT;1 (1 block)
-
- > Is there any way to avoid this (other than have no login.com)?
-
- Yes, if the first line of your login com turns off verify:
- $ verify = 'f$verify(0)
-
- Ken
-