Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!mimsy!chris
From: chris@mimsy.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Two process communication programs
Message-ID: <6947@mimsy.UUCP>
Date: Fri, 5-Jun-87 23:07:10 EDT
Article-I.D.: mimsy.6947
Posted: Fri Jun  5 23:07:10 1987
Date-Received: Sun, 7-Jun-87 00:44:15 EDT
References: <2071@emory.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 14
Keywords: rlogin tip cu

In article <2071@emory.UUCP>, km@emory.UUCP (Ken Mandelberg) writes:
>... why the extra process in tip and rlogin, which are relatively
>recent and written just for BSD?

I cannot speak for tip, never having used it, but rlogin supports
a `partially stopped' mode (via ~^Y, or whatever your delayed
suspend character is) in which output from the remote system is
still displayed.  For this to work rlogin must fork.  Given that,
it might as well do it immediately.  (There may also be less overhead
that way, as the two processes can just sit in read() and write();
a successful select() would require at least one more system call.)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	seismo!mimsy!chris