bin/81555: Cron exits from SIGPIPE after crontab -e when
usingNSS-LDAP
Thomas Sandford
freebsduser at paradisegreen.co.uk
Thu Jun 30 15:40:15 GMT 2005
The following reply was made to PR bin/81555; it has been noted by GNATS.
From: "Thomas Sandford" <freebsduser at paradisegreen.co.uk>
To: "Dick Davies" <rasputnik at hellooperator.net>
Cc: <bug-followup at FreeBSD.org>, <dean at stack.nl>, <rasputnik at hellooperator.net>,
<nectar at FreeBSD.org>
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" <rasputnik at hellooperator.net>
> ...
>
> 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
More information about the freebsd-bugs
mailing list