Re: FreeBSD getpwuid_r issue
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
Re: FreeBSD getpwuid_r issue
- From: Aragon Gouveia <aragon [at] phat.za.net>
- To: nss-pam-ldapd-users [at] lists.arthurdejong.org
- Subject: Re: FreeBSD getpwuid_r issue
- Date: Tue, 04 Mar 2014 21:23:33 +0200
Hi Arthur,
Thanks for responding!
On 03/04/14 20:51, Arthur de Jong wrote:
Is this the version from ports or plain from source? If self-compiled,
which flags were used? What is the contents of /etc/nsswitch.conf?
It's the version from ports.
The only thing that I can think of is that bash is compiled differently
from other binaries (perhaps if compat is used in /etc/nsswitch.conf).
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...
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
Thanks,
Aragon
--
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
http://lists.arthurdejong.org/nss-pam-ldapd-users/