[is the glibc maintainers mailing list still the correct venue?]
Hi,
I really appreciate your help, it is insightful.
On Wed, Jul 06, 2022 at 04:57:47PM -0400, Carlos O'Donell wrote:
> On Wed, Jul 6, 2022 at 10:10 AM Marc Haber
> wrote:
> > On Wed, Jul 06, 2022 at 09:29:22AM -0400, Carlos
On Wed, Jul 6, 2022 at 10:10 AM Marc Haber wrote:
> On Wed, Jul 06, 2022 at 09:29:22AM -0400, Carlos O'Donell wrote:
> > You can verify that nscd is catching the cases you care about by running
> > it in '--debug' mode to let you see the cache invalidation.
>
> I regret to say that I don't use
Hi Carlos,
thank you for commenting.
I am one of the adduser maintainers in Debian and we would like to ditch
the parts of our code that invalidate nscd explicitly in one of the
future versions of the software.
On Wed, Jul 06, 2022 at 09:29:22AM -0400, Carlos O'Donell wrote:
> You can verify
On Mon, Jul 4, 2022 at 3:30 PM Marc Haber wrote:
> adduser still has code to invalidate nscd cache after doing changes to
> the user database. I would like to get rid of this and just document
> that people using nscd should use the provided hook to invalidate their
> nscd cache after creating or
[Please Cc: me on replies, I am not subscribed to Debian-glibc]
Hi,
adduser still has code to invalidate nscd cache after doing changes to
the user database. I would like to get rid of this and just document
that people using nscd should use the provided hook to invalidate their
nscd cache after
5 matches
Mail list logo
