Date: Wed, 01 Feb 2012 00:03:20 +0100 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Current FreeBSD <freebsd-current@freebsd.org> Subject: using nscd (ldap) makes passwd/group disappearing while installing ports Message-ID: <4F287338.8000002@zedat.fu-berlin.de>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig39CD2492D1AA6F893ACDCA3A Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable I'm using on a couple of servers the nameservice cache dameon nscd and cache "group", "passwd" and "sudoers". Backend is LDAP, but local files should searched first. then ldap. cache is searched the very first even before files. Well, I'd expect that if a group is present, like "cups" or "dhcp" and reside in the local file (/etc/group or /etc/passwd), they are cached. Installing net/isc-dhcp42-server fails with this error: gmake[1]: Leaving directory `/usr/ports/net/isc-dhcp42-server/work/dhcp-4.2.3-P2/server' gmake[1]: Entering directory `/usr/ports/net/isc-dhcp42-server/work/dhcp-4.2.3-P2' gmake[1]: Nothing to be done for `all-am'. gmake[1]: Leaving directory `/usr/ports/net/isc-dhcp42-server/work/dhcp-4.2.3-P2' =3D=3D=3D> Installing for isc-dhcp42-server-4.2.3_2 =3D=3D=3D> Generating temporary packing list =3D=3D=3D> Creating users and/or groups. Creating group `dhcpd' with gid `136'. pw: group disappeared during update *** Error code 70 Stop in /usr/ports/net/isc-dhcp42-server. *** Error code 1 Stop in /usr/ports/net/isc-dhcp42-server. I also have this error very often when rebuilding/updating or even installing cups when "nscd" is enabled. A simple restart of nscd helps in most cases, most times I need to disable "cache" tag in /etc/nsswitch.conf, then everything runs smooth. Well, this behaviour is since a couple of years now, occurs sporadic. I have had in FreeBSD 7, 8, 9 and I see it in 10. What is it? I like the cache facility, since in domains with a lot of users searching LDAP takes some time and caching help keeping traffic and latency short. But the namservice caching mechanism seems to be unreliable. What is up there? --------------enig39CD2492D1AA6F893ACDCA3A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBAgAGBQJPKHNBAAoJEOgBcD7A/5N8qgYIANhc8Q7K6Jgif+j93ig0RivP qWpK0OXBsUocQiW6LGi3XDM0IwN3VXawLp+xxFOtI73JqNTvweimmJ/DBjnAPEJS xbbsnKiVZzs8qvgO9jwBi+/q6OXaFPnoPkX5Icn5l12+N08s3h4EyEny6LcEq7DB hlmOMEwa6QXGyjhgS9wNnqRWaj761QcJGHx+J5Pov27oYNt04eycSYPGFUPAVCSa UuMbsJF7XChGZeYu9wWY2F8UST1/3wZJdIe9d1unZk4Gr4mmQc/icdbjRBaUxk0C AJ3Sm3Ji86AMZoOymY00Sgp/G9O48BqP6eV35yyCaOPUcbGDrmSI3kpbceThTgo= =jf+c -----END PGP SIGNATURE----- --------------enig39CD2492D1AA6F893ACDCA3A--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F287338.8000002>