Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!amdahl!pacbell!varian!david
From: david@varian.UUCP (David Brown)
Newsgroups: comp.sys.att
Subject: Re: Users of Wollongong's WIN/3B Release 2.1
Summary: we had problems too
Message-ID: <704@varian.UUCP>
Date: 16 Feb 89 03:37:50 GMT
References: <928@cs.rit.edu>
Distribution: usa
Organization: Varian, Walnut Creek CA
Lines: 29


Well, you're not alone - we also had problems, especially in
regards to remsh.  First, incoming remsh from other machines
had problems - after the command completed, the connection
never closed and the user never got his prompt back.  I called
the Hotline and they sent me a fix for this (plus a fix for
an rlogin problem in relationship to Suns).  The other problem
was outgoing remsh - I was doing backups similar to you:
	find . -print | remsh another-machine dd of=/dev/tape

and the throughput was abysmal - I could watch the lights on
the transceiver and see that packets were sent only once every
5 seconds.  The Hotline couldn't help, and the problem was
escalated. Months later, I finally received a fix disk from
a different group (in Illinois) and finally we were back to
the level of functionality that we had with rel 1.1 (except
for some header files and socket calls that they seem to have
dropped - I was able to compile and execute ping and a few
other Berkeley programs with 1.1, but not 2.1).

So others have had problems, and there are fixes - you should hammer
on them.  I've heard that there will be a new version (2.2) coming
out very shortly, but since I haven't received any official notice,
I expect that it's really months away.

-- 
David Brown	 415-649-4000
Orion Network Systems 1995 University Ave. Suite 350 Berkeley CA 94704
{pacbell,lll-crg,zehntel,ista,rtech,csi,kinetics}!varian!david