[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#330929: marked as done (how can adduser reliably find out wheter nscd is running?)

Your message dated Sun, 15 Apr 2007 13:01:12 +0200
with message-id <20070415110112.GA31920@artemis>
and subject line Bug#330929: how can adduser reliably find out wheter nscd is running?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: nscd
Severity: wishlist

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
appropriate arguments.

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.

Greetings
Marc

-- 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)

--- End Message ---
--- Begin Message --- 
On Fri, Sep 30, 2005 at 04:05:40PM +0200, Marc Haber wrote:
> Package: nscd
> Severity: wishlist
> 
> 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
> appropriate arguments.
> 
> 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?

  well, Why don't you try to do "pidof nscd" ? that would give you a
good idea. okay, it does not work on the hurd, but some alike method
would do no ? (like ps ax | grep -q 'sbin/nsc[d]'


  Else, I'd go for the "looking for the two possible pid paths", which
is reasonable and harmless IMHO.

  Btw (I know the bug is very old) please rather come on
debian-glibc@l.d.o for such questions in the future :)

Cheers,
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: pgpP00tHNbQYc.pgp
Description: PGP signature


--- End Message ---
Reply to: