[3458] in Kerberos
kerberos V rlogin isn't resizing right.
daemon@ATHENA.MIT.EDU (David Blob)
Wed Jun 22 23:58:03 1994
To: kerberos@MIT.EDU
Date: Wed, 22 Jun 1994 19:42:33 GMT
From: blob@idaho.syl.dl.nec.com (David Blob)
Ok, I've tried and I've tried, but I'm giving up...
I'll just ask the question...
Why doesn't kerberos V rlogin resize right on suns...?
I've tried it all...I've gotten the newest version
of rlogin, and I've kerberized it, and I've got the
same problems...
I looked a little deeper...it sure seems like the
code is right...I've run tcpdump...my machine is
getting the urgent data which should set off a
sigurg in the parent or the child...make its way
to the child, and go on...but its just not...
i've added code to syslog, and well, sometimes I
get vastly different behavior...sometimes it appears
as if neither the parent or the child got the SIGURG.
This is usually if I just run it...
Sometimes, the parent gets it and signals the child,
but when the child calls recv to get the OOB data,
and find out what request it is, it chokes, get this,
with errno EINVAL... EINVAL isn't a valid error for
receive, and all the parameters sure seem valid...
This usually happens when run with trace...
then sometimes, very rarely, and usually under gdb
or trace, it just seems to work...only because I've
run it under gdb or trace it isn't usable...
So...has anyone gotten kerberos V rlogin working
right on a sun??? the rlogin protocol appears to
me to be very time sensitive...are there race
conditions???
What am I missing...???
-Dave
