From owner-freebsd-bugs@FreeBSD.ORG Thu Jun 30 15:40:14 2005 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E96EB16A42A for ; Thu, 30 Jun 2005 15:40:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2EC443D48 for ; Thu, 30 Jun 2005 15:40:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5UFeE5h090158 for ; Thu, 30 Jun 2005 15:40:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j5UFeEdG090157; Thu, 30 Jun 2005 15:40:14 GMT (envelope-from gnats) Date: Thu, 30 Jun 2005 15:40:14 GMT Message-Id: <200506301540.j5UFeEdG090157@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Thomas Sandford" Cc: Subject: Re: bin/81555: Cron exits from SIGPIPE after crontab -e when usingNSS-LDAP X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Thomas Sandford List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 15:40:15 -0000 The following reply was made to PR bin/81555; it has been noted by GNATS. From: "Thomas Sandford" To: "Dick Davies" Cc: , , , Subject: Re: bin/81555: Cron exits from SIGPIPE after crontab -e when usingNSS-LDAP Date: Thu, 30 Jun 2005 16:39:32 +0100 >* "Dick Davies" > ... > > I'm guessing cron looks up a uid in a non-nss aware way somehow and dies > when it can't find > them, but I don't really know enough of the system to explain further. I've done some more digging. The real bug is in nss_ldap. The current FreeBSD port is of a 2 year old version and from comments in the changelog in the current version of nss_ldap this bug is known and fixed. [the bug has been found before - as I understand it, nss_ldap doesn't mask signals correctly, and if the connection to the server has closed a SIGPIPE error is generated. nss_ldap masks, but doesn't ignore this signal and so continues on, but when the signal is unmasked the cron (or whatever) process gets the signal. D'oh!]. Unfortunately the current nss_ldap version (239 vs 204 in FreeBSD ports) cannot be compiled by the ports harness "as-is" as there are changes to the patched files - there also appears to be a bug in the Makefile.in for this version. I'm seeing if I can come up with some revised patches for this port to get it to build. [Maintainer for ports/net/nss-ldap copied on this email/followup]. -- Thomas Sandford