On Apr 20, 2009, at 09:43, Scott Haneda wrote:
On Apr 20, 2009, at 7:25 AM, Daniel J. Luke wrote:
$sudo /opt/local/sbin/postfix start
dyld: Library not loaded: /opt/local/lib/mysql5/mysql/
libmysqlclient.16.dylib
Referenced from: /opt/local/sbin/postfix
Reason: image not found
Trace/BPT
Why did mysql allow it?
On Apr 20, 2009, at 7:25 AM, Daniel J. Luke wrote:
You upgrade mysql and it removed a library that postfix depended on.
(/opt/local/lib/mysql5/mysql/libmysqlclient.16.dylib).
When you removed and re-installed postfix, it found the newer mysql
library and worked agai
You upgrade mysql and it removed a library that postfix depended on. (/
opt/local/lib/mysql5/mysql/libmysqlclient.16.dylib).
When you removed and re-installed postfix, it found the newer mysql
library and worked again.
One way of dealing with this sort of thing would be to have a staging
s
I uninstalled postfix, and put it back in, this all went away. I
would like to know what caused this, and how to avoid it. These are
often going to be production servers, and things like this happening
would be bad. If I know what is going on, I can prepare for them and
make sure I do no
$port -v
MacPorts 1.710
$port installed | grep -i postfix
postfix @2.5.5_0+darwin_9+dovecot_sasl+ldap+mysql5+tls (active)
$whereis postfix
/usr/sbin/postfix
* Is whereis hard coded in standard paths, and that is not something I
can change?
$which postfix
/opt/local/sbin/postfix
$echo $PAT
