From owner-freebsd-ports Fri Nov 13 13:49:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06371 for freebsd-ports-outgoing; Fri, 13 Nov 1998 13:49:59 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06363 for ; Fri, 13 Nov 1998 13:49:58 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id NAA13178; Fri, 13 Nov 1998 13:50:01 -0800 (PST) Date: Fri, 13 Nov 1998 13:50:01 -0800 (PST) Message-Id: <199811132150.NAA13178@freefall.freebsd.org> To: freebsd-ports@FreeBSD.ORG From: Jacques Vidrine Subject: Re: ports/8609: eklogin service (kerberos klogind) fails to print DES msg Reply-To: Jacques Vidrine Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/8609; it has been noted by GNATS. From: Jacques Vidrine To: freebsd-gnats-submit@freebsd.org, cschuber@uumail.gov.bc.ca, dima@freebsd.org Cc: Subject: Re: ports/8609: eklogin service (kerberos klogind) fails to print DES msg Date: Fri, 13 Nov 1998 15:49:13 -0600 The same behavior is seen under -CURRENT. The patch in question defines HAVE_OPENPTY. This causes the Kerberos utility library to use openpty rather than the code built into Kerberos (pty_getpty) for allocating a master pty. I've determined that the difference that tickles this bug between the openpty code and the pty_getpty code is that openpty opens the slave as well as the master, while pty_getpty just opens the master. I was able to recreate the bug by undefining HAVE_OPENPTY (so that the built-in pty_getpty code would be used), but adding a gratuitous open/close of the slave pty in krlogind.c. i.e. something like: if ((retval = pty_getpty(&p,line, sizeof(line)))) { com_err(progname, retval, "while getting master pty"); exit(2); } + { + int dummy = open(line, O_RDWR, 0); + if (dummy) + close(dummy); + } So I am theorizing that some state change caused by the open and/or close of the tty is occurring that is tickling some bug. Unfortunately, I'm not familiar enough with the terminal drivers to understand what. -- Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message