Leisner.Henr@xerox.com (Marty) (03/18/90)
Between two machines (a sun386i and a sun3/280) I can: 1) rlogin both ways with no problem 2) rsh both ways with no problem 3) rcp only one way (sun386i initiates the transfer). The sun3 is running SunOS 3.5. The sun386i is running SunOS 4.0.1. The sun386i can send/receive stuff via rcp from the sun3. On the sun 3: 1) when I send it fails silently 2) when I try to bringover a file I get: rcp: protocol screwup: mtime.sec not delimited I'm stumped -- what should I look for? marty ARPA: leisner.henr@xerox.com GV: leisner.henr NS: leisner:wbst139:xerox UUCP: hplabs!arisia!leisner
mason@oct1.UUCP (David Mason) (03/28/90)
From article <22782@adm.BRL.MIL>, by Leisner.Henr@xerox.com (Marty): > > Between two machines (a sun386i and a sun3/280) I can: > 1) rlogin both ways with no problem > 2) rsh both ways with no problem > 3) rcp only one way (sun386i initiates the transfer). > > The sun386i can send/receive stuff via rcp from the sun3. I've seen a similar thing on ISC 386/ix 2.0.2. It may be unrelated, but it may not. The problem was that one could only fetch remote large files, and not move big files local->remote. The cause was the ulimit. On V.3.2, the ulimit defaults to about 2000 blocks, and can be reset in /etc/default/login for all logins. However, /usr/ucb/r* utilities are poorly ported up to V.3.2 by Interactive, and do not read any of the /etc/default/* files. This problem was discussed in October '89 on the net. Anyway, the ulimit was too low, so you couldn't write large files remotely. Maybe you should check this area. -------------------- David | mason@oct1 (David Mason) | ...!uunet!ddsw1!olsa99!oct1!mason
rob@violet.berkeley.edu (Rob Robertson) (04/15/90)
From article <22782@adm.BRL.MIL>, by Leisner.Henr@xerox.com (Marty):
Between two machines (a sun386i and a sun3/280) I can:
1) rlogin both ways with no problem
2) rsh both ways with no problem
3) rcp only one way (sun386i initiates the transfer).
The sun386i can send/receive stuff via rcp from the sun3.
this is because of how rcp works: rcp when doing a "rcp a:file b:file"
from machine c (ie from one remote machine to another remote machine)
will remotely exec an (using rcmd(3)) an "rcp file b:file on machine
a. this requires that machine b have an entry in it's .rhosts for
machine a.
yes, this is kindda bogus.
rob
--
william robertson
rob@violet.berkeley.edu
indecision is the key to flexiblity