From:
[email protected]
I cannot believe Steve Greenland said this on the ENTARNET:
On 09-Jul-04, 09:11 (CDT), [email protected] wrote:
Using nscd instead of direct libnss-ldap<->slapd makes the problema go away.
Right. The pam_ldap people won't fix their module to catch SIGPIPE, the expect every application using it to change. Of course, the applications dont' *know* that they're using ldap, that being the whole point of PAM,
and there's no reason to expect SIGPIPE from getpwent().
To be fair, they have a legitimate concern, because the application
could be trapping SIGPIPE for some other purpose, and having pam_ldap
catch them would cause the original to be lost. But there are ways to accomodate these, and since either way breaks existing applications, I'd
vote for going the way that breaks the fewest. The pam_ldap developers disagree.
So nscd is the way to go.
I've been having this same problem with cron, even in conjunction with
nscd. I've narrowed the cause down to crontab replacements. These
are consistently the last two log entries after I modify a crontab:
Aug 21 13:08:01 goose cron[17358]: nss_ldap: reconnecting to LDAP server...
Aug 21 13:08:02 goose cron[17358]: nss_ldap: reconnected to LDAP server after 1 attempt(s)
After these two log entries, cron is dead. This is on a system which
uses nscd.
-Nate
--
--< ((\))< >----<
[email protected] >----<
http://www.movealong.org/ >-- pub 1024D/05A058E0 2002-03-07 Nate Riffe (06-Mar-2002) <
[email protected]>
Key fingerprint = 0DAC F5CB D182 3165 D757 C466 CD42 12A8 05A0 58E0
--
To UNSUBSCRIBE, email to
[email protected]
with a subject of "unsubscribe". Trouble? Contact
[email protected]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)