No, it doesn't; it just
seems like Postfix is starting succesfully.
Quote:
krab:/bin# ps -ef | grep postfix
krab:/bin# ps -ef | grep zimbra
zimbra 15426 1 0 17:57 pts/1 00:00:00 /usr/bin/perl /opt/zimbra/libexec/zmmtaconfig
zimbra 15630 1 0 17:58 ? 00:00:00 amavisd (master)
zimbra 15646 15630 0 17:58 ? 00:00:00 amavisd (virgin child)
zimbra 15647 15630 0 17:58 ? 00:00:00 amavisd (virgin child)
zimbra 15648 15630 0 17:58 ? 00:00:00 amavisd (virgin child)
zimbra 15649 15630 0 17:58 ? 00:00:00 amavisd (virgin child)
zimbra 15650 15630 0 17:58 ? 00:00:00 amavisd (virgin child)
zimbra 15654 15630 0 17:58 ? 00:00:00 amavisd (virgin child)
zimbra 15655 15630 0 17:58 ? 00:00:00 amavisd (virgin child)
zimbra 15656 15630 0 17:58 ? 00:00:00 amavisd (virgin child)
zimbra 15657 15630 0 17:58 ? 00:00:00 amavisd (virgin child)
zimbra 15658 15630 0 17:58 ? 00:00:00 amavisd (virgin child)
zimbra 15847 1 0 17:58 ? 00:00:00 /opt/zimbra/clamav/bin/freshclam --config-file=/opt/zimbra/conf/freshclam.conf -d --checks=12
zimbra 15867 1 0 17:58 ? 00:00:00 /opt/zimbra/clamav/sbin/clamd --config-file /opt/zimbra/conf/clamd.conf
root 19573 12246 0 18:22 pts/1 00:00:00 grep zimbra
|
All commands listed above starting with a $ were executed as user zimbra, the ones with # as root.
Quote:
|
krab:/opt/zimbra# sh -x ./bin/postfix start
|
yields the same output as running it as user zimbra, and still there's no Postfix running.