On Sun, 20 Jul 2008 20:19:05 +1000, Damien Miller wrote:
>> > My suspicion is that syslogd has not yet finished >> > making the log socket and the "postfix check" that >> > happens at postfix start fails. > > That shouldn't happen, because syslogd delays its exit until after > its log sockets have been established. Damien, I am not so sure if it is syslog that fails. I have something else failing before, please see my maillog in the ports@: Jul 11 11:56:19 claude authdaemond: modules="authuserdb authpwd authpgsql authld ap authmysql authpipe", daemons=5 Jul 11 11:56:19 claude authdaemond: Installing libauthuserdb Jul 11 11:56:19 claude authdaemond: File not found Jul 11 11:56:19 claude authdaemond: Installing libauthpwd Jul 11 11:56:19 claude authdaemond: Installation complete: authpwd Jul 11 11:56:19 claude authdaemond: Installing libauthpgsql Jul 11 11:56:19 claude authdaemond: File not found Jul 11 11:56:19 claude authdaemond: Installing libauthldap Jul 11 11:56:19 claude authdaemond: File not found Jul 11 11:56:19 claude authdaemond: Installing libauthmysql Jul 11 11:56:19 claude authdaemond: File not found Jul 11 11:56:19 claude authdaemond: Installing libauthpipe Jul 11 11:56:19 claude authdaemond: Installation complete: authpipe Jul 11 11:56:20 claude postfix/postfix-script[17841]: fatal: Postfix integrity c heck failed! I am not aware that I'd use courier-authlib for that postfix, but who knows what it checks? in any case, postfix seems to wait for something, that slower machines cannot provide fast enough. If you have any idea how to debug this and find out *what* it can't find, let me know, Uwe
