-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Guillaume Cottenceau wrote:
> Following bug #3967, I'd like to add a
> /usr/share/doc/postfix-2.0.12/MANDRAKE.SPECIFIC.CHROOT_README
> file. I'd write something like the following. Please share with
> me your wise comments on it.
>
Instead of providing documentation on the long way to fix it, why not
provide an easier way to fix it?
> -----8<----------8<----------8<----------8<----------8<-----
>
> For example, if your /etc/resolv.conf is updated when you launch
> the network on your laptop, you will want to create a file named
> /etc/sysconfig/network-scripts/ifup.d/postfix containing:
>
> -=-=---=-=---=-=---=-=---=-=---=-=--
> #!/bin/sh
> # update resolv.conf in postfix chroot environment
> cp -f /etc/resolv.conf /var/spool/postfix/etc/resolv.conf > /dev/null
> -=-=---=-=---=-=---=-=---=-=---=-=--
>
> You may want to update also other files depending on your
> configuration.
Why not have the postfix init script check an option in a /etc/sysconfig
file for a descriptive variable (POSTFIX_ALWAYS_UPDATE_CHROOT), and if
it is true, check every file under /var/spool/postfix/{var,usr,lib} to
see if a newer one is outside the chroot, if so, update the one in the
chroot.
IMHO, postfix should be restarted when an interface comes up (if it was
running).
Regards,
Buchan
- --
|--------------Another happy Mandrake Club member--------------|
Buchan Milne Mechanical Engineer, Network Manager
Cellphone * Work +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering http://www.cae.co.za
GPG Key http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/Cb89rJK6UGDSBKcRAlYWAJwNv6JpoII0HiO/yExGX8Viups9UgCgu18H
t/jaAWUB80IJ6ZO0sVqIcyo=
=Y+Il
-----END PGP SIGNATURE-----
******************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
******************************************************************
