Hi Tomasz,
Thanks for your reply. The problem appears to be related syslog. If I turn
of syslogd, the problem is gone. If I configure all jabberd2 components to
log to file instead of syslog, the problem is also gone. I don't know why
changing mysql from unix socket to tcp/ip would make syslog
Hi,
I'm new to jabberd2, and am having some performance problems when
moving mysql to an separate machine.
I installed jabberd-2.14 on the same machine as mysql 5.0, such that
jabberd2 communicates with mysql via the unix /tmp/mysql.sock. Things
are running nice and fast, load testing
