zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: borsenkow.msk@sni.de,
	Zsh users mailing list <zsh-users@math.gatech.edu>,
	<hzoli@vnet.ibm.com> (Zoltan T. Hidvegi)
Cc: "Timothy J. Luoma" <luomat@peak.org>
Subject: Re: problem from NeXTStep 3.3 rlogin to SunOS 4.1.4
Date: Wed, 5 Mar 1997 09:39:36 -0800	[thread overview]
Message-ID: <970305093937.ZM6479@candle.brasslantern.com> (raw)
In-Reply-To: Andrej Borsenkow <borsenkow.msk@sni.de> "Re: problem from NeXTStep 3.3 rlogin to SunOS 4.1.4" (Mar  5,  9:47am)
In-Reply-To: <hzoli@vnet.ibm.com> (Zoltan T. Hidvegi) "Re: problem from NeXTStep 3.3 rlogin to SunOS 4.1.4" (Mar  5, 10:54am)
In-Reply-To: Andrej Borsenkow <borsenkow.msk@sni.de> "Re: problem from NeXTStep 3.3 rlogin to SunOS 4.1.4" (Mar  5,  7:09pm)

On Mar 5,  9:47am, Andrej Borsenkow wrote:
} Subject: Re: problem from NeXTStep 3.3 rlogin to SunOS 4.1.4
}
} rlogin SINIX-L -> SINIX-N shows the above problem. It is not always the
} whole output lost - sometimes I see only the first line of `ls' output;
} sometimes the `CR NL' after prompt is lost

On Mar 5, 10:54am,  (Zoltan T. Hidvegi) wrote:
} Subject: Re: problem from NeXTStep 3.3 rlogin to SunOS 4.1.4
}
} Do you use setopt no_flow_control?  If yes, did you try to unset it?

On Mar 5,  7:09pm, Andrej Borsenkow wrote:
} Subject: Re: problem from NeXTStep 3.3 rlogin to SunOS 4.1.4
}
} thousand thanks! running with
}   `unsetopt no_flow_control'
} really helps (I havn't set it - it must be on by default). 

Did you unset this in the local shell before starting rlogin, or in the
remote shell afterwards?  (I suspect the remote one.)

} It is probably still OS bug (happens with rlogin only - telnet runs O.K.),
} but as long as workaround exists I don't care.

This begins to sound more and more familiar.  Is the stty line speed
slower on the local terminal where you started rlogin than it is on the
remote psuedo-tty?  If so, you might try forcing them to be the same to
see if that also makes the problem go away.

The rlogin processes probably want to use flow control to compensate for
the different line speeds.

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


  reply	other threads:[~1997-03-05 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-03-04 19:04 Timothy J. Luoma
1997-03-04 22:20 ` Bart Schaefer
1997-03-05  6:47 ` Andrej Borsenkow
1997-03-05 15:54   ` Zoltan T. Hidvegi
1997-03-05 16:09     ` Andrej Borsenkow
1997-03-05 17:39       ` Bart Schaefer [this message]
1997-03-05 16:45     ` Timothy Luoma

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=970305093937.ZM6479@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=borsenkow.msk@sni.de \
    --cc=hzoli@vnet.ibm.com \
    --cc=luomat@peak.org \
    --cc=schaefer@nbn.com \
    --cc=zsh-users@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).