"Perhaps invoking postfix to run earlier, just after configuring network interfaces, would be a better solution?"
I don't think so. Starting it before would mean: a) starting postfix with a temporary invalid resolv.conf (might create problems with any security check postfix run on startup) b) changing resolv.conf while postfix is running They are not huge problems, but I think it's better to set the resolving before starting any smtpd, named or whatever. Actually, the very first solution that came to my mind was to completely delete the postfix reload thingie: but thinking at it a little more made me discover that there were a case where it could be useful; when, for example, you have to reaload your network service and/or change network card settings without having to reboot or manually reload services. With my patch we have a clean startup (not starting anything before the "basics" are up and running) and we still cover the (rare) case in which the network service needs to be reloaded on a "hot" machine, and we want to keep the services running while this happens. Best regards, Simone -- resolvconf update-libc error https://launchpad.net/bugs/41302 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
