Hi again -
I have a problem with rmt on Digital Unix V3.2. When I try to use our
TLZ06 drive remotely with rdump or other third-party products, I get the
following activity in rmt (which exits after reporting the error).
I captured the output as per the man page instructions, by renaming the
rmt executable to rmt.ORG and placing a script called rmt in /usr/sbin which
goes as follows:
#!/bin/csh -f
/usr/sbin/rmt.ORG /tmp/rmt/debug
exit
The debug output is always the same:
rmt: O /dev/rmt0h 2
rmt: A 0
rmt: I 5 1
rmt: A 1
rmt: I 5 1
rmt: A 1
rmt: R 80
rmt: cannot set socket receive-buffer size
rmt: checkbuf(): setsockopt(): No such file or directory
I thought that the Multinet software on our VAX (VMS 5.5) was the problem, but
it happens with other alphas, running Digital Unix V3.0 (was it still OSF/1
then?). However I can only even get this far some of the time. The rest of
my efforts to startup up rmt (using rdump) return the error:
Permission denied.
rdump: Cannot establish connection to remote rmt command
rmthost(): rcmd(): Invalid argument
Terminated
Has anyone seen this behaviour? And does anyone know how it is fixed?
Thanks and as always a summary will follow.....
Brian
--
Brian Sheehan
The Scripps Research Institute
La Jolla, CA
(619)554-6651
sheehan_at_ruska.scripps.edu
Received on Tue Jun 06 1995 - 05:26:15 NZST