Re: FreeBSD getpwuid_r issue

[Arthur de Jong <arthur [at] arthurdejong.org>]

On Tue, 2014-03-04 at 21:23 +0200, Aragon Gouveia wrote:
> I'll try experiment with the bash compilation.  It's worth pointing
> out though that cron is causing similar error logs:
> 
> Mar  4 15:33:00 <cron.debug> cstor1 cron[63321]: NSSWITCH(_nsdispatch): ldap, 
> group, setgrent, not found, and no fallback provided
> Mar  4 15:33:00 <cron.debug> cstor1 cron[63321]: NSSWITCH(_nsdispatch): ldap, 
> group, getgrent_r, not found, and no fallback provided
> Mar  4 15:33:00 <cron.debug> cstor1 cron[63321]: NSSWITCH(_nsdispatch): ldap, 
> group, endgrent, not found, and no fallback provided
> Mar  4 15:33:00 <cron.debug> cstor1 cron[63321]: NSSWITCH(_nsdispatch): ldap, 
> passwd, endpwent, not found, and no fallback provided
> Mar  4 15:35:00 <cron.debug> cstor1 cron[63335]: NSSWITCH(_nsdispatch): ldap, 
> passwd, getpwnam_r, not found, and no fallback provided
> 
> Will see what I can dig up...

Perhaps some FreeBSD people can provide more details. In any case, I'm
very interested in the results and the underlying problem.

> My nsswitch.conf:
> 
> group: ldap files
> group_compat: nis
> hosts: files dns
> networks: files
> passwd: ldap files
> passwd_compat: nis
> shells: files
> services: compat
> services_compat: nis
> protocols: files
> rpc: files

You only need group_compat and passwd_compat lines if you are using
compat somewhere else. Also, it is highly recommended to put files
before ldap to avoid some issues when your LDAP server is unavailable.

Unless you also use NIS, services should probably point to files alone.

-- 
-- arthur - arthur@arthurdejong.org - http://arthurdejong.org/ --

-- 
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
http://lists.arthurdejong.org/nss-pam-ldapd-users/