From: Date: March 3 2005 3:44pm
Subject: ulimit effects on mysql user?
List-Archive: http://lists.mysql.com/mysql/180816
Message-Id: <2BAA38D980E9BC448E1FC4DFCEA658BF02A3A0@win-em-2.red-man.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C51FFF.70751358"

------_=_NextPart_001_01C51FFF.70751358
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

if I have changed my /etc/security/limits.conf file to include these =
lines:
=20
mysql    soft      nofile        4096
mysql    hard     nofile        63536
=20
and then done:
=20
[root@rh-mysql-1 root]# su mysql
[mysql@rh-mysql-1 root]$ ulimit -n 8192
[mysql@rh-mysql-1 root]$ ulimit -n
8192

does this new 8192 open file limit apply to the already-running mysqld =
process, which was started like so:
=20
[root@rh-mysql-1 root]# /usr/local/mysql/bin/mysqld_safe --user=3Dmysql =
&
=20
? or will I need to restart the mysql server and/or machine to have the =
new open files limit take effect for the mysql server? am I correct that =
the open files limit placed on the mysql user will be the limit faced by =
the mysqld process, since the process is started with the --user=3Dmysql =
option?
=20
thanks,
-L

------_=_NextPart_001_01C51FFF.70751358--