Re: problem from NeXTStep 3.3 rlogin to SunOS 4.1.4

["Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>]

On Mar 4,  2:04pm, Timothy J. Luoma wrote:
} Subject: problem from NeXTStep 3.3 rlogin to SunOS 4.1.4
}
} When I rlogin to my SUN account from my NeXT, I have been "losing"  
} output.  Most often it happens with 'ls' or 'cat' where the command  
} runs but nothing comes to the screen.

Do you really mean "rlogin"?  As in, you log in to the Sun, get a prompt,
and then start issuing "ls" and "ls | less" commands?

Or do you mean "rsh" as in "rsh sun ls" vs. "rsh sun ls | less"?

} If I feed it to 'less' that works.
} 
} Any clues?

If it's "rsh" then this is (or used to be) a common problem.  It happens
when the rsh process on the local side exits before the output buffered
in the network layer gets flushed to the screen.

The local rsh exits when it gets notified on the exit-status connection
that the remote process has terminated; that may leave unread data on
the stdout/stderr connections.  If some other process (like less) is
waiting for the output, or if the output is sufficiently large, the
buffers get flushed before local rsh exits (before the shell gets control
back again).

I don't know why it would have begun happening to you now if it wasn't
before, but in my experience the problem isn't limited to zsh.

-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern