Bug #4017
closedpostfix package looking for /usr/local on pfsense 2.2
0%
Description
I'm seeing these while trying to start posfix on 2.2 BETA
/usr/pbi/postfix-amd64/sbin/postfix start
cd: /usr/local/libexec/postfix: No such file or directory
postfix/postfix-script: fatal: no Postfix daemon directory /usr/local/libexec/postfix!
After manual link creation
ln -s /usr/pbi/postfix-amd64/local/libexec/postfix /usr/local/libexec/postfix
ln -s /usr/pbi/postfix-amd64/local/etc/postfix /usr/local/etc/postfix
/usr/pbi/postfix-amd64/sbin/postfix -c /usr/pbi/postfix-amd64/etc/postfix start
postfix/postfix-script: fatal: the Postfix mail system is already running
But it's not running
And getting this while trying to stop
/usr/pbi/postfix-amd64/sbin/postfix -c /usr/pbi/postfix-amd64/etc/postfix stop
postfix/postfix-script: stopping the Postfix mail system
sed: pid/master.pid: No such file or directory
usage: kill [-s signal_name] pid ...
kill -l [exit_status]
kill -signal_name pid ...
kill -signal_number pid ...
Shared object "libsasl2.so.3" not found, required by "master"
postfix/postfix-script: waiting for the Postfix mail system to terminate
Shared object "libsasl2.so.3" not found, required by "master"
postfix/postfix-script: waiting for the Postfix mail system to terminate
Shared object "libsasl2.so.3" not found, required by "master"
postfix/postfix-script: waiting for the Postfix mail system to terminate
Shared object "libsasl2.so.3" not found, required by "master"
postfix/postfix-script: waiting for the Postfix mail system to terminate
Shared object "libsasl2.so.3" not found, required by "master"
postfix/postfix-script: waiting for the Postfix mail system to terminate
postfix/postfix-script: warning: stopping the Postfix mail system with force
awk: can't open file pid/master.pid
source line number 1
Updated by Chris Buechler almost 10 years ago
that looks to be a general issue with a number of packages, #4018 covers that general issue
Updated by Renato Botelho almost 10 years ago
- Status changed from New to Rejected
Will track all those issues in #4018