With login 1:4.16.0-2+really2.40.4-5 in.rlogind immediately
disconnects as it can't handle the "vhangup" call used by login.

See also Bug#1078023, it seems that rlogind needs some special
handling to handle a read returning EIO; I have found this in the
telnetd source code:

 * In particular, EIO is known to appear when
 * reading off the master side, before having
 * an active slave side.


Note that rlogind works fine with earlier versions of login that don't
use vhangup.

There appears to be a race condition -- it occasionally works,
but usually disconnects.