On Wednesday 06 April 2016, Christian Boltz wrote:
> Hello,
>
> Am Mittwoch, 6. April 2016, 18:07:26 CEST schrieb Ruediger Meier:
> ...
>
> > I really hate that nscd. I've had also problems with it a few years
> > ago on 11.4. (crashs, 100% CPU, ...). I wonder why the glibc people
> > do not fix it. Instead they have added a "paranoia" mode to restart
> > it regularly:
> > http://serverfault.com/questions/463648/why-would-nscd-use-a-huge-a
> >mou nt-of-ram
> >
> > I'll try /etc/nscd.conf:
> >         paranoia                yes
> >         restart-interval        3600
>
> You'll probably need to adjust the AppArmor profile a bit to allow
> that. Otherwise, nscd won't be able to restart itsself (which
> effectively means ignoring the paranoia mode).
>
> https://bugzilla.opensuse.org/show_bug.cgi?id=971790

Thanks, good to know.

There seems to be another bug
$ nscd --invalidate
does not to work.

The only way to reset cache and stats is to set 
  persistent   xyz           no
and rcnscd.restart.


> The profile needs to allow reading /proc/$pid/cmdline, which means
> you'll need to add the rule
>   @{PROC}/@{pid}/cmdline r,
>
> The easiest way is probably:
>     echo '@{PROC}/@{pid}/cmdline r,' >>
> /etc/apparmor.d/local/usr.sbin.nscd rcapparmor reload

How would I disable appamor system wide?

> This is fixed in the upstream profile (including the upcoming 2.9.3
> and 2.10.1 releases), but I slightly doubt this is worth an update
> for Evergreen ;-)
>
>
> Regards,
>
> Christian Boltz
_______________________________________________
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen

Reply via email to