Package: sasl2-bin Version: 2.1.22.dfsg1-23 Severity: important File: /usr/sbin/saslauthd
On upgrading to lenny, I found that saslauthd would no longer start. Although README.Debian describes *optional* configuration of multiple instances, the init script makes this configuration mandatory even if only a single instance is required. If OPTIONS is not set then it should assume that saslauthd's socket and state will appear in the default directory (/var/run/saslauthd), but instead it fails. Also, it should not warn that NAME is set if only a single instance is configured. Ben. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-6-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sasl2-bin depends on: ii db4.6-util 4.6.21-11 Berkeley v4.6 Database Utilities ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libc6 2.7-18 GNU C Library: Shared libraries ii libcomerr2 1.41.3-1 common error description library ii libdb4.6 4.6.21-11 Berkeley v4.6 Database Libraries [ ii libkrb53 1.6.dfsg.4~beta1-5 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.11-1 OpenLDAP libraries ii libpam0g 1.0.1-5 Pluggable Authentication Modules l ii libsasl2-2 2.1.22.dfsg1-23 Cyrus SASL - authentication abstra ii libssl0.9.8 0.9.8g-15 SSL shared libraries ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip sasl2-bin recommends no packages. sasl2-bin suggests no packages. -- debconf information: cyrus-sasl2/upgrade-sasldb2-failed: * cyrus-sasl2/backup-sasldb2: /var/backups/sasldb2.bak cyrus-sasl2/upgrade-sasldb2-backup-failed: cyrus-sasl2/purge-sasldb2: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org