Bug#330929: how can adduser reliably find out wheter nscd is running?
adduser needs to invalidate certain nscd tables after changes were
done. Today, it looks for the pid file of nscd to find out whether
nscd is running, and then calls nscd via system() with -i and the
However, this heuristics has recently begun to fail because the
pidfile has moved from /var/run to /var/run/nscd. Instead of changing
adduser to check for both files (and probably fail on the next
location change), I'd like to have a clearly drawn interface to find
out whether it is necessary to invalidate nscd or not.
What do you, as nscd maintainer(s) recommend to have adduser do?
Thanks for your opinion.
-- System Information:
Debian Release: testing/unstable
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13-zgsrv
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)