On 2007-11-27 14:15:29 +0200, [EMAIL PROTECTED] wrote:
> I agree that it’s kind strange behavior.
>
> Also I’ve googled that exactly the same errors (unexpected eof
> found … on file ‘UNOPENED’) were related to mysql.
> But how mysql compile options might affect configuration file parsing
> and r
I agree that it’s kind strange behavior.
Also I’ve googled that exactly the same errors (unexpected eof
found … on file ‘UNOPENED’) were related to mysql.
But how mysql compile options might affect configuration file parsing
and read/write operations? (indexes for example) Does any one have
any i
On 2007-11-27 11:21:16 +0200, [EMAIL PROTECTED] wrote:
> I have found similar problem:
> http://www.dovecot.org/list/dovecot/2007-January/018623.html
> "After configure remove HAVE_PREAD from config.h, recompile and see
> if it works."
>
> I think I figured out where might be the problem. If th
I have found similar problem:
http://www.dovecot.org/list/dovecot/2007-January/018623.html
"After configure remove HAVE_PREAD from config.h, recompile and see
if it works."
I think I figured out where might be the problem. If the binary is
compiled in the 64bit environment and you want to use
