Jeremy Chadwick wrote:
> On Sun, May 20, 2007 at 07:25:04PM -0400, Paul Laudanski wrote:
>> Steven Hartland wrote:
>>> Should be able to just roll your ports tree back to when it included
>>> 5.1.X or manually update the couple of files required and then rebuild.
>>> That said it may not be that wh
Jeremy Chadwick wrote:
> On Sun, May 20, 2007 at 07:25:04PM -0400, Paul Laudanski wrote:
>> Steven Hartland wrote:
>>> Should be able to just roll your ports tree back to when it included
>>> 5.1.X or manually update the couple of files required and then rebuild.
>>> That said it may not be that wh
Jeremy Chadwick wrote:
> On Sun, May 20, 2007 at 07:25:04PM -0400, Paul Laudanski wrote:
>> Steven Hartland wrote:
>>> Should be able to just roll your ports tree back to when it included
>>> 5.1.X or manually update the couple of files required and then rebuild.
>>> That said it may not be that wh
On Sun, May 20, 2007 at 07:25:04PM -0400, Paul Laudanski wrote:
> Steven Hartland wrote:
> > Should be able to just roll your ports tree back to when it included
> > 5.1.X or manually update the couple of files required and then rebuild.
> > That said it may not be that which is causing your issue
Kris Kennaway wrote:
> On Sun, May 20, 2007 at 06:43:37PM -0400, Paul Laudanski wrote:
>> I ugpraded from mysql 5.1.15 to 5.1.18 via portsupgrade, and now cannot
>> run mysql. Errors:
>>
>> 070520 22:41:09 mysqld started
>> 070520 22:41:09 [Warning] Server variable data_file_path of plugin
>> Inn
Steven Hartland wrote:
> Should be able to just roll your ports tree back to when it included
> 5.1.X or manually update the couple of files required and then rebuild.
> That said it may not be that which is causing your issue check to see if
> you enhancing the memory sizes using the following, N.
Should be able to just roll your ports tree back to when it included 5.1.X or manually update the couple of files required and
then rebuild. That said it may not be that which is causing your issue check to see if you enhancing the memory sizes using the
following, N.B. adjust sizes to be appropr
On Sun, May 20, 2007 at 06:43:37PM -0400, Paul Laudanski wrote:
> I ugpraded from mysql 5.1.15 to 5.1.18 via portsupgrade, and now cannot
> run mysql. Errors:
>
> 070520 22:41:09 mysqld started
> 070520 22:41:09 [Warning] Server variable data_file_path of plugin
> InnoDB was forced to be read-on
l.sock' port: 0 FreeBSD
port: mysql-server-5.1.18
070520 22:41:33 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed
1676960 bytes)
This seems familiar:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/packages-using.html
I have 8GB on this 64 bit AMD system.
It appear
