Bug#330929: how can adduser reliably find out wheter nscd is running?
On Tue, Oct 04, 2005 at 02:41:26PM +0200, Marc Haber wrote:
> Adduser has _a lot_ of installations and is mainly used by maintainer
> scripts. Thus, _a lot_ of people are bound to see error messages
> generated by adduser and are bound to be confused by them.
>
> > Or you can just add "2>/dev/null" to the nscd -i
> > invocation.
>
> That will also kill "real" error messages.
Are there any useful "real" error messages now? For example, if nscd is
not running, trying to invalidate a non-existing map will not produce an
error message, and if nscd is running, the error message is misleading.
I still prefer not fixing what is not broken. glibc upgrades are always
complex and require lots of testing. So I think even if nscd behavior is
changed upstream in the future, there will be enough time before the
next Debian release to discover any problems and update adduser if
neccessary.
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences,
Laboratory of Parallel and Distributed Systems
Address : H-1132 Budapest Victor Hugo u. 18-22. Hungary
Phone/Fax : +36 1 329-78-64 (secretary)
W3 : http://www.lpds.sztaki.hu
---------------------------------------------------------
Reply to: