Thanks for your support. I solved the problem based on your suggestions. I creaded a chroot environment by bind-mounting / to another directory, then overloading /etc/pam.d/ and /var/run/saslauthd/ with bind mounts of my secondary saslauthd PAM configuration and socket/data directories. After mounting /proc inside the chroot, even the CentOS saslauthd initscript worked without changes, so a new initscript simply executing 'chroot /chroot/dir /etc/init.d/saslauthd "$1"' controls my second saslauthd well. Best regards, // Veit
