Comment 5 for bug 927803

I think this is a bug in both postfix and friendly-recovery.

- resolvconf will always be run in early boot, to ensure that /etc/resolv.conf is available ASAP - *before* the root filesystem is mounted read-write. Any resolvconf hooks, such as /etc/resolvconf/update-libc.d/postfix, *must* account for this and not exit non-zero if the filesystem is not yet writable. (The hook can and should be a no-op at this point in the boot, because the postfix init script which runs later will do its own copy of /etc/resolv.conf into the chroot.)

- friendly-recovery should not care about the exit status of the initctl emit command. It should still wait for all dependent events to trigger in order to not race, but it should not care if one of the dependent jobs has failed.

So this is a medium-severity bug in friendly-recovery, and a high-severity bug in postfix.