Processed: Re: Bug#331405: Accidential activation of nscd is too simple

2007-03-06 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reassign 331405 libpam-ldap Bug#331405: Accidential activation of nscd is too simple Bug reassigned from package `nscd' to `libpam-ldap'. tags 331405 patch Bug#331405: Accidential activation of nscd is too simple There were no tags set. Tags added

Bug#331405: Accidential activation of nscd is too simple

2007-03-06 Thread Helmut Grohne
reassign 331405 libpam-ldap tags 331405 patch thanks It would be libpam-ldap which suggests libnss-ldap in my case. But running apt-rdepends and analyzing it's output suggests that there are 35 packages which depends on nscd in etch today. That's depends as in any of the relationships that

Bug#331405: Accidential activation of nscd is too simple

2005-10-08 Thread LESUEUR Francois
(Hoping I'm doing things right, first time for me...) Gabor Gombas @ 2005-10-05 (Wednesday), 16:08 (+0200) Also, the default negative-ttl for the hosts map is just 20 seconds which I think _is_ a quite reasonable default. If twenty seconds were the case, I wouldn't have complained. I had

Bug#331405: Accidential activation of nscd is too simple

2005-10-05 Thread Gabor Gombas
On Mon, Oct 03, 2005 at 12:33:45PM +0200, Martin Samuelsson wrote: Obviously something has automatically dragged nscd into my system as one of it's dependencies. (It's marked A in aptitude) And having a software cacheing dns lookups from disconnected moments doesn't really make a laptop very

Bug#331405: Accidential activation of nscd is too simple

2005-10-05 Thread Martin Samuelsson
Gabor Gombas @ 2005-10-05 (Wednesday), 16:08 (+0200) What is that something? Investigating the output of apt-cache rdepends nscd, libnss-pgsql1 and libnss-mdns Suggests: nscd, and libnss-ldap Recommends: it, but nothing Depends: on it. So you should've given a choice by whatever package

Bug#331405: Accidential activation of nscd is too simple

2005-10-03 Thread Martin Samuelsson
Package: nscd Version: 2.3.5-6 Severity: important After some time of random dns failures I started tracking the problem today, the first time I found a reproducable way to trigger it. Obviously something has automatically dragged nscd into my system as one of it's dependencies. (It's marked A