OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: MySQL trouble on 3.5-stable

From: . kibble . (jelly_bean_junkyhotmail.com)
Date: Wed Dec 22 2004 - 10:19:15 CST


>On Wed, 22 Dec 2004 Nico Meijer wrote<nico.meijerzonnet.nl>
>In a perhaps feeble attempt to try anything, I've introduced the
>following into /etc/login.conf and killed and started MySQL again:
>mysql:\
> :datasize=infinity:\
> :maxproc=infinity:\
> :openfiles-cur=2048:\
> :openfiles-max=8192:\
> :stacksize-cur=8M:\
> :localcipher=blowfish,8:\
> :tc=default:
>
>In about twelve hours, I'll know if this helped or not... ;-)

In my login.conf I have:
mysql:\
        :datasize=infinity:\
        :maxproc=infinity:\
        :openfiles-cur=1772:\
        :openfiles-max=8192:\
        :stacksize-cur=8M:\
        :localcipher=blowfish,8:\
        :tc=default:

The reason why I have '1772' in my openfiles-cur is because when I had it
set to '2048' such as you do, MySQL server made error logs very much like
this when it started up:
041113 5:49:21 [Warning] Could not increase number of max_open_files to
more than 1772 (request: 2048)

Have a look in your .err file and see what it says when you restart your
MySQLd ? Also check for any other errors that may well be in there and let
us know...

I'm using oBSD3.6 and MySQL 4.1.8... Running very nicely may I add on a
550MHz K6-AMD with 256MBs of RAM and 13GB hard drive.

_________________________________________________________________
It's fast, it's easy and it's free. Get MSN Messenger today!
http://www.msn.co.uk/messenger