On Thu, 13 Jan 2000, Eric J. Schwertfeger wrote:
> I've also tested non-localhost lsh in both directions between A and C, and
> it looks like whatever the problem is, it is in lshd. B is behind a
> firewall blocking port 22, so I can't test it until I get onto that
> machine and run lshd on a different port.
My mistake, it had nothing to do with the lshd. It had to do with the
fact that machine A was the only one of the bunch with a disk subsystem
that would let ls -lR / outrun lsh/lshd. As soon as I piped the output to
a file, then cat the file, the error turned up on all three machines.
