[6241] in Kerberos
Re: SIGINT in the rlogind child
daemon@ATHENA.MIT.EDU (Sam Hartman)
Thu Nov 16 11:59:40 1995
To: Gary Gaskell <gaskell@dstc.edu.au>
Cc: kerberos@MIT.EDU, krb5-bugs@MIT.EDU
In-Reply-To: Your message of "Thu, 16 Nov 1995 17:40:37 +1000."
<Pine.OSF.3.91.951116172917.9535G-100000@foxtail.dstc.edu.au>
Date: Thu, 16 Nov 1995 11:42:30 EST
From: Sam Hartman <hartmans@MIT.EDU>
>>>>> "Gary" == Gary Gaskell <gaskell@dstc.edu.au> writes:
Gary> Version details: V5 beta 5 on DEC OSF/1 v 3.2 Background:
Gary> Using kerbersied rlogin to secure connections between
Gary> research labs on different university campuses. Some users
Gary> complained that a ^C on the rlogin client caused the rlogin
Gary> session itself to abort, rather than just to kill some
Gary> process they were running on the remote computer.
I would be interested in which operating systems this happens on. I know it happens on SunOS, Solaris, and now OSF.
Gary> SIGINT is ignored in the client, but the ^C is sent to the
Gary> server, where it kills the child. This kills the session,
Gary> and the client reports "Connection Closed".
This confuses me. The krlogind child shouldn't exist any more
as it should have been replaced by the shell. If you mean it kills
krlogind, then that's really puzzling (although I think that is
probably what is happening), because krlogind should not be in the
foreground process group of that tty. I would appreciate any comments
explaining what's happening; I haven't had time to really track down
the problem, although I will eventually get to it if no one else knows
what is failing.
Gary> So I got into krlogind.c and in the child , told it to
Gary> ignore any SIGINT signals.
Gary> The question: Any reason why this should not be done?
If it fixes your problem and you aren't interested in finding
the real bug, this is a quick fix. This may end up being the right
solution, but I am reluctant to make this change to our source tree
until I understand what process is getting killed, and why it gets the
sigint signal. It is my understanding that most shells ignore sigint so I'm not sure I see what is happening unless krlogind itself is getting the kill signal. If this is the case, I am really confused, because as I said above, it should be in the wrong process group.
Again, this is a rather annoying problem, and we will fix it;
this bug as well as SunOS utmp handling is at the top of my to-do list
for telnetd and krlogind.
Gary> Have I missed something and it should be configured
Gary> elsewhere? So far my modification works and my users are
Gary> happy.
--Sam
