Package: nss-updatedb Version: 7-1.1 Severity: important Hi there,
We have been using nss-updatedb on alioth (a slightly patched version to temporarily work around a bug in nss-pgsql) and we have noticed that the database updates are not atomic. We frequently get exim panicking that it can't find a user it has just decided to suid to, or svn commits failing, or that sort of thing. I'd like to work with you to resolve this - my first thought is to switch to writing files in a temporary subdirectory, and then move them across - while that doesn't eliminate the race condition, it should lessen it. Take care, -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-xen-amd64 Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Versions of packages nss-updatedb depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libdb4.3 4.3.29-8 Berkeley v4.3 Database Libraries [ Versions of packages nss-updatedb recommends: ii libnss-db 2.2.3pre1-2 NSS module for using Berkeley Data -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
