z]
Sent: Monday, January 11, 2010 12:59 PM
To: tajoli
Cc: Chadwick, John, DCA; koha-devel@lists.koha.org
Subject: Re: [Koha-devel] Stack smashing resolved -- we think
2010/1/12 tajoli :
> Hi,
>
>> Our server has 8GB of memory with a quad core processor. I allocated
>> 1000GB to the
to time?
Thanks,
John
-Original Message-
From: Chris Cormack [mailto:ch...@bigballofwax.co.nz]
Sent: Monday, January 11, 2010 12:59 PM
To: tajoli
Cc: Chadwick, John, DCA; koha-devel@lists.koha.org
Subject: Re: [Koha-devel] Stack smashing resolved -- we think
2010/1/12 tajoli :
>
Right now we are building the system and adding records in 500 record
chunks.
John
-Original Message-
From: tajoli [mailto:taj...@cilea.it]
Sent: Monday, January 11, 2010 12:44 PM
To: Chadwick, John, DCA
Cc: koha-devel@lists.koha.org
Subject: Re: [Koha-devel] Stack smashing resolved
2010/1/12 tajoli :
> Hi,
>
>> Our server has 8GB of memory with a quad core processor. I allocated
>> 1000GB to the MyISAM sort buffer size. I also increased the key buffer
>> size. I found a few things about memory, but not much, on the Koha Wiki.
>> I would like to hear from others what you have
Hi,
> Our server has 8GB of memory with a quad core processor. I allocated
> 1000GB to the MyISAM sort buffer size. I also increased the key buffer
> size. I found a few things about memory, but not much, on the Koha Wiki.
> I would like to hear from others what you have found to be optimal
> memo
Okay, it looks like the stack smashing issue has been resolved through
increased allocation of memory in several places on the MySQL server.
Our server has 8GB of memory with a quad core processor. I allocated
1000GB to the MyISAM sort buffer size. I also increased the key buffer
size. I found
he mystery deepens.
John
-Original Message-
From: MJ Ray [mailto:m...@phonecoop.coop]
Sent: Wednesday, January 06, 2010 4:08 AM
To: Chadwick, John, DCA
Cc: koha-devel@lists.koha.org
Subject: Re: [Koha-devel] Stack Smashing
"Chadwick, John, DCA" wrote: [...]
> *** stack smashing
"Chadwick, John, DCA" wrote: [...]
> *** stack smashing detected ***: zebraidx terminated
> === Backtrace: =
> /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb6d7cda8]
> /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb6d7cd60]
> /usr/lib/libidzebra-2.0.so.0[0xb7fc10c4]
> /usr/
]
Sent: Tuesday, January 05, 2010 11:23 AM
To: Chadwick, John, DCA
Cc: koha-devel
Subject: Re: [Koha-devel] Stack Smashing
On 2010/01/6, at 7:07 AM, Chadwick, John, DCA wrote:
> Here is a good challenge. I have seen this question posed a few
> times, but have not seen an answer. We are r
On 2010/01/6, at 7:07 AM, Chadwick, John, DCA wrote:
> Here is a good challenge. I have seen this question posed a few
> times, but have not seen an answer. We are running 3.01.00.061 on
> Ubuntu 8.04.3. Using the icuchain method for indexing records.
>
>
>
> When we got to just over 10,000 r
Here is a good challenge. I have seen this question posed a few times,
but have not seen an answer. We are running 3.01.00.061 on Ubuntu
8.04.3. Using the icuchain method for indexing records.
When we got to just over 10,000 records we started to get the following
error message when Zebra gets
11 matches
Mail list logo
