On Wednesday 14 December 2005 15:59, Roger Kvam wrote:
> Now I`m really embarrassed, actually ,FreeBSD is protecting itself
> against runaway processes by allowing maximum memory size for one
> process to 512MB, I had to increase the maximum to 2 gig by adding
> kern.maxdsiz=2147483648 to /boot/loa
Heigl Florian - Munich-MR - external wrote:
Hi Roger,
Now I`m really embarrassed, actually ,FreeBSD is protecting itself
against runaway processes by allowing maximum memory size for one
process to 512MB, I had to increase the maximum to 2 gig by adding
kern.maxdsiz=2147483648 to /boot/loader
Hi Roger,
> Now I`m really embarrassed, actually ,FreeBSD is protecting itself
> against runaway processes by allowing maximum memory size for one
> process to 512MB, I had to increase the maximum to 2 gig by adding
> kern.maxdsiz=2147483648 to /boot/loader.conf. witch is my physical
> amount o
Hello,
I repeat what I said the last time: this looks like a MySQL problem. Given the
new information you have presented, and the fact that you are having problems
when working with almost 9 million files backed up (a lot), I would suspect
that the problem is with your MySQL configuration. If
This looks to me like a problem with MySQL. Did you by any chance load
pre-built binaries rather than build on your system. My best guess at the
moment is that Bacula is built with version X of MySQL and you are running
with version Y on your machine. That means that some of the packet fields
