On Wed, May 26, 2004 at 10:55:25AM -0400, Ted Zlatanov wrote:
> On 26 May 2004, [EMAIL PROTECTED] wrote:
>
> > Your misunderstanding something. If the user is in ldap then qmail-getpw
> > will not be run.
>
> But it was. I saw the qmail-getpw processes hung, blocking local
> deliveries!
>
> > So either the ldap lookup fails or it is not qmail-getpw that hangs
> > -- qmail-lspawn will probably also do a stat for autohomedir
> > creation.
>
> I know qmail-getpw hung after being invoked by a qmail-ldap component.
> I also confirmed that it hung by tracing it, and confirming it was
> doing stat("/home/tzz"). I am sure the user 'tzz' was in LDAP at the
> time, but I don't know for sure that the LDAP lookup succeeded (there
> was no message about a lookup failure in the logs).
>
> > I guess you are using mailmessagestore and homedirectory together and
> > therefor qmail-ldap is using homedirectory as $HOME and will stat it. So
> > you should recompile qmail with LDAP_HOMEDIR set to "noHomeDirectory" in
> > qmail-ldap.h or modify the OpenLDAP ACL so that homeDirectory is not
> > returned.
>
> Both the homeDirectory and mailmessagestore for user 'tzz' are set to
> a non-NFS location, see my original message. /home/tzz is coming
> only from NIS through getpwnam().
>
> I'll test more over the weekend when the mail server is not so
> heavily used, and I'll manually disable all /home mounts. Thank you
> for your help.
>
To log issues with ldap and local lookups just set the LOGLEVEL to
something like 20.
I can gruarantee you that qmail-getpw only gets run if
~control/ldaplocaldelivery is non 0 and the user is NOT in LDAP.
hopefully you find out what causes the troubles.
--
:wq Claudio
