Hi,
Here's what I did to fix my problem in AIX 4.3.3 ML08. Your problem looks a
little different.
Booker C. Bense was nice enough to send me this:
- It's under AIX and written by Sam Hartman.
Here's the patch to krlogind.c
Index: krlogind.c
===================================================================
RCS file: /afs/ir/dev/cvs/kerberos/krb5/appl/bsd/krlogind.c,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- krlogind.c 2001/07/23 20:55:50 1.7
+++ krlogind.c 2001/08/29 21:21:34 1.8
@@ -996,7 +996,7 @@
int on = 1;
#endif
-#if defined(TIOCPKT) && !defined(__svr4__) || defined(solaris20)
+#if defined(TIOCPKT) && !defined(__svr4__) && !defined(_AIX) ||
defined(solaris20)
/* if system has TIOCPKT, try to turn it on. Some drivers
* may not support it. Save flag for later.
*/
Kevin
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, January 11, 2002 7:52 AM
> To: [EMAIL PROTECTED]
> Subject: Re: CTRL+C hangs RSH and RLOGIN
>
> I have looked everywhere and can't find this patch. Can you please be
> specific and give us a URL or something? I did find one copy but it
> crashed when I tried to apply it. (It came out as one line of ascii
> and my many guesses at reformatting it could all have been wrong)
>
> On AIX, rsh hangs if .profile is present, and in rlogin su and ksu
> both hang.
>
> Thanks, Julian.
>
> [EMAIL PROTECTED] (Tom Yu) wrote in message
> news:<[EMAIL PROTECTED]>...
> > >>>>> "bbense" == Booker C Bense <[EMAIL PROTECTED]>
> writes:
> >
> > bbense> On Wed, 12 Dec 2001, Kevin wrote:
> > >> Is there something similar I can do with RSH or RLOGIN.
> > >>
> >
> > bbense> - It's a bug in the src code. Look in the krb-bugs email
> > bbense> archive for the patch.
> >
> > I believe the patch will be included in our upcoming 1.2.3 release.
> >
> > ---Tom
This electronic message transmission, including any attachments, contains information
from PacifiCare Health Systems Inc. which may be confidential or privileged. The
information is intended to be for the use of the individual or entity named above. If
you are not the intended recipient, be aware that any disclosure, copying,
distribution or use of the contents of this information is prohibited.
If you have received this electronic transmission in error, please notify the sender
immediately by a "reply to sender only" message and destroy all electronic and hard
copies of the communication, including attachments.
