Postfix init.d script and populate chroot in multi-instance environment [debian bug #560682]

Binary package hint: postfix

Copy/paste from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560682

I hit the pb on Ubuntu Lucid :

===== description of the problem

  When running postfix daemon in chroot environment we need to assure
that the chroot dir is up-to-date (aka. etc/services lib/*, ...).

  For a single instance this is done by the /etc/init.d/postfix script.

  Starting with 2.6.x, Postfix supports now the multi-instance concept
(http://www.postfix.org/MULTI_INSTANCE_README.html). So for each
instance, we have a new /var/spool/postfix-instance that is created and
where daemons may be run as chrooted.

  The problem with the /etc/init.d/postfix script distributed by Debian
(in version 2.6.5-3) is that it does not take of the multi-instance
chroot dirs : the script only synchronizes the default instance (aka
/etc/postfix) and not all the other instances. So in a chroot
environment, with a chroot dir not synchronized we may have some
problems like "fatal: unknown service: smtp/tcp".

===== workaround

  I think the init.d script need to be adjust to take care of the
multi-instance chroot dir.

  Please see the attached patch
"postfix-init.d--multiinstance-chroot-aware.patch".

  It does 2 things :
    - iterate on each instance declared in the default one (postmulti
-l) and do the job that was done in the past
    - we have to synchronize some other file like "/dev/log" and
"/lib/libresolv*so*"