The cause of the failure in /etc/resolvconf/update-libc.d/postfix is here: QUEUEDIR="$(/usr/sbin/postconf2 -h queue_directory 2>/dev/null || true)"
# /usr/sbin/postconf2 -h queue_directory 2>/dev/null # echo $? 127 # This is because: # /usr/sbin/postconf2 -h queue_directory bash: /usr/sbin/postconf2: No such file or directory # So, I don't know why this is 'postconf2' instead of 'postconf', but it's definitely broken. However, I also see that the version of the script shipped in the package does *not* show this bug; so maybe this is an invalid bug report and my issue is caused by a local change when I was testing resolvconf integration previously (i.e., to make sure a failing hook doesn't cause resolvconf as a whole to fail). The file was last updated in May 2012, which is quite a while ago. I don't know why this is causing a behavior change on my system in practice; probably something in raring has changed boot timing here and postfix is now starting faster. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1118549 Title: postfix regression in raring: fails to pick up dynamic resolv.conf changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1118549/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
