[net.bugs.4bsd] Rlogind eats Cpu time.

steveh@hammer.UUCP (Stephen Hemminger) (05/10/84)

Index:	/etc/rlogind

Description:
	Rlogind chews away time while trying to send to a remote user
	who has blocked his rlogin process (either by stopping it or
	hitting ^S).

Repeat-By:
	rlogin to another host.  cat a big file (/etc/termcap).
	Then stop the rlogin process (~^Z).
	Do a ps on the remote machine and look at the rlogind process.

Fix:	None.
	The earlier suggested fix (which causes the write to block)
	is unacceptable since it makes pipe's non-atomic.

	Someone must have noticed and fixed this by now!

thomson@uthub.UUCP (Brian Thomson) (05/22/84)

The fix I posted in December does not make the write block,
it permits partial writes on non-blocking stream sockets.
The complaint that this makes pipes non-atomic is unjustified,
because pipes in 4.2BSD are already non-atomic.
-- 
		    Brian Thomson,	    CSRG Univ. of Toronto
		    {linus,ihnp4,uw-beaver,floyd,utzoo}!utcsrgv!uthub!thomson