Re: ulimit for mysql and www-data
I had the same problem (with apache) , and found that the best way is to add ulimit -n 32000 ulimit -u 2048 at the begining of /etc/init.d/apache And I think that is the best way to do it. sometning like /etc/rc.boot/ulimit_optimize possibly won't work, because limits are inherited through fork() , and to execute your script, the init fork()s,exec() your script,the parent waits for the end of it's execution, and then continues, so he shouldn't see the change in the limits. (sorry for my rusty english :) ) On Wed, 26 Dec 2001, Patrick Hsieh wrote: > Hello list, > > I am running a dedicated apache/php/mysql website on Debian 3.0(woody). > MySQL server runs as "mysql" uid; Apache "www-data". It seems that the > default ulimit value does not meet the requirement as a dedicated machine. > The Debian GNU/Linux box ships dual PentiumIII-1G with 1G RAM. I am planing > to optimize the ulimit value for "www-data" and "mysql", any suggestions? > > BTW, I am planing to put some optimization scripts under /etc/rc.boot, say > /etc/rc.boot/fs_optimize > (tuning /proc/sys/fs/*) > > /etc/rc.boot/ulimit_optimize > (tuning ulimit stuff) > > Is it a good way to put ulimit adjustments for www-data and mysql in > /etc/rc.boot/ulimit_optimize so that it works upon boot time? > > Any suggestions appreciated.
Re: ulimit for mysql and www-data
I had the same problem (with apache) , and found that the best way is to add ulimit -n 32000 ulimit -u 2048 at the begining of /etc/init.d/apache And I think that is the best way to do it. sometning like /etc/rc.boot/ulimit_optimize possibly won't work, because limits are inherited through fork() , and to execute your script, the init fork()s,exec() your script,the parent waits for the end of it's execution, and then continues, so he shouldn't see the change in the limits. (sorry for my rusty english :) ) On Wed, 26 Dec 2001, Patrick Hsieh wrote: > Hello list, > > I am running a dedicated apache/php/mysql website on Debian 3.0(woody). > MySQL server runs as "mysql" uid; Apache "www-data". It seems that the > default ulimit value does not meet the requirement as a dedicated machine. > The Debian GNU/Linux box ships dual PentiumIII-1G with 1G RAM. I am planing > to optimize the ulimit value for "www-data" and "mysql", any suggestions? > > BTW, I am planing to put some optimization scripts under /etc/rc.boot, say > /etc/rc.boot/fs_optimize > (tuning /proc/sys/fs/*) > > /etc/rc.boot/ulimit_optimize > (tuning ulimit stuff) > > Is it a good way to put ulimit adjustments for www-data and mysql in > /etc/rc.boot/ulimit_optimize so that it works upon boot time? > > Any suggestions appreciated. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ulimit for mysql and www-data
Hello list, I am running a dedicated apache/php/mysql website on Debian 3.0(woody). MySQL server runs as "mysql" uid; Apache "www-data". It seems that the default ulimit value does not meet the requirement as a dedicated machine. The Debian GNU/Linux box ships dual PentiumIII-1G with 1G RAM. I am planing to optimize the ulimit value for "www-data" and "mysql", any suggestions? BTW, I am planing to put some optimization scripts under /etc/rc.boot, say /etc/rc.boot/fs_optimize (tuning /proc/sys/fs/*) /etc/rc.boot/ulimit_optimize (tuning ulimit stuff) Is it a good way to put ulimit adjustments for www-data and mysql in /etc/rc.boot/ulimit_optimize so that it works upon boot time? Any suggestions appreciated. -- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDwn/AERBADMjSQLy6ql+PYYaTg82VNgTVV7BLqffOLbLCYvt7fLkM9WNcPU hWCIFu2T8nIpniww7lPg7CrhoeOhohB59mF76bRZ2ZfxAHOo5JYgvc6RU5YzbwIT +rGffrhsNayCK34V3ylEFvJlor2dO7nHuxGJ7+KR2Xt7T4YDQPkOh3Ii9wCgptqL n3iAKX8FXh6pTyCnwoSADaUEAK1laNT4tkCXvluIRxc+aDy6UHlpnDEVZspvytd0 j0sGeLTyxDWQmm5iyJ0LuX1u9ShGsIFPu1auo4bVhiwkNsNaYfZ6z1CjMB+1QesA cAHeLGwQTUi1StF9GcWCWtqzffh3/xvQu/jKbfmtWrQk3NcB8GtyWgfjhO5vEU2r aY3aBAC28kSahK0SzKNPFaDiJ+Ckf/D31s8Dl1MvAW1bI5iiBWUwKxK7OaQHu6BJ FBrvn7tXJmm7Fn7al2O794NEQ2MlfBi6E4IrmTp74YYqUvtBdNnKQe5f/wgiG8Vr f3RDVjPR3ejQUFfjagv/DADvm52FJRebWatqOjuw1RWf4sf3CLQnUGF0cmljayBI c2llaCAoUGFodWQpIDxwYWh1ZEBwYWh1ZC5uZXQ+iFcEExECABcFAjwn/AEFCwcK AwQDFQMCAxYCAQIXgAAKCRAxtsLiID998RmQAJ9ct/aZYKlui+uSp+ZmogSTGu9i DQCfTs1R0L0ZTEPuJJi40Hald98YW2S5AQ0EPCf8AxAEAN7rZj2rNKjbuG42Dvsx SOuYvPGj7uql9yERRcMsXPoPwk3aY/sObvHMnvGYDZngXKYFvV3eeiutoTtvksh1 yUM2LYvv2HL8lloCJmjMv3YYO5FUkvmD2wN5y5zhN6zsNQc9zc9fb17xnRI7RbOC jITdJlA27ov6B0WjauCB5zqTAAMGBADUTVHIJrWRE7rV5ZhcxypcOmz5N9RGdXTb h0ckyLXKnRu/c3gCo6adM5RdNBkC6Pe6T8xUvtSyGHGuhLKHkNZlMWihBau3XYGQ aiyrgOaPuIiJ7rKUAKV4mpElh2WJcEbNAMPNirvOGClSaQIdVrUpEfiLAh1SGiT4 f5dmg1+814hGBBgRAgAGBQI8J/wDAAoJEDG2wuIgP33xd54An30UwY1c21Hm8TV1 080PiIT6MLiFAJ9+P+PGpRYWR2KPo0UEjcfBFmFwXg== =p11n -END PGP PUBLIC KEY BLOCK- pgpzyGnxyOAxJ.pgp Description: PGP signature
ulimit for mysql and www-data
Hello list, I am running a dedicated apache/php/mysql website on Debian 3.0(woody). MySQL server runs as "mysql" uid; Apache "www-data". It seems that the default ulimit value does not meet the requirement as a dedicated machine. The Debian GNU/Linux box ships dual PentiumIII-1G with 1G RAM. I am planing to optimize the ulimit value for "www-data" and "mysql", any suggestions? BTW, I am planing to put some optimization scripts under /etc/rc.boot, say /etc/rc.boot/fs_optimize (tuning /proc/sys/fs/*) /etc/rc.boot/ulimit_optimize (tuning ulimit stuff) Is it a good way to put ulimit adjustments for www-data and mysql in /etc/rc.boot/ulimit_optimize so that it works upon boot time? Any suggestions appreciated. -- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDwn/AERBADMjSQLy6ql+PYYaTg82VNgTVV7BLqffOLbLCYvt7fLkM9WNcPU hWCIFu2T8nIpniww7lPg7CrhoeOhohB59mF76bRZ2ZfxAHOo5JYgvc6RU5YzbwIT +rGffrhsNayCK34V3ylEFvJlor2dO7nHuxGJ7+KR2Xt7T4YDQPkOh3Ii9wCgptqL n3iAKX8FXh6pTyCnwoSADaUEAK1laNT4tkCXvluIRxc+aDy6UHlpnDEVZspvytd0 j0sGeLTyxDWQmm5iyJ0LuX1u9ShGsIFPu1auo4bVhiwkNsNaYfZ6z1CjMB+1QesA cAHeLGwQTUi1StF9GcWCWtqzffh3/xvQu/jKbfmtWrQk3NcB8GtyWgfjhO5vEU2r aY3aBAC28kSahK0SzKNPFaDiJ+Ckf/D31s8Dl1MvAW1bI5iiBWUwKxK7OaQHu6BJ FBrvn7tXJmm7Fn7al2O794NEQ2MlfBi6E4IrmTp74YYqUvtBdNnKQe5f/wgiG8Vr f3RDVjPR3ejQUFfjagv/DADvm52FJRebWatqOjuw1RWf4sf3CLQnUGF0cmljayBI c2llaCAoUGFodWQpIDxwYWh1ZEBwYWh1ZC5uZXQ+iFcEExECABcFAjwn/AEFCwcK AwQDFQMCAxYCAQIXgAAKCRAxtsLiID998RmQAJ9ct/aZYKlui+uSp+ZmogSTGu9i DQCfTs1R0L0ZTEPuJJi40Hald98YW2S5AQ0EPCf8AxAEAN7rZj2rNKjbuG42Dvsx SOuYvPGj7uql9yERRcMsXPoPwk3aY/sObvHMnvGYDZngXKYFvV3eeiutoTtvksh1 yUM2LYvv2HL8lloCJmjMv3YYO5FUkvmD2wN5y5zhN6zsNQc9zc9fb17xnRI7RbOC jITdJlA27ov6B0WjauCB5zqTAAMGBADUTVHIJrWRE7rV5ZhcxypcOmz5N9RGdXTb h0ckyLXKnRu/c3gCo6adM5RdNBkC6Pe6T8xUvtSyGHGuhLKHkNZlMWihBau3XYGQ aiyrgOaPuIiJ7rKUAKV4mpElh2WJcEbNAMPNirvOGClSaQIdVrUpEfiLAh1SGiT4 f5dmg1+814hGBBgRAgAGBQI8J/wDAAoJEDG2wuIgP33xd54An30UwY1c21Hm8TV1 080PiIT6MLiFAJ9+P+PGpRYWR2KPo0UEjcfBFmFwXg== =p11n -END PGP PUBLIC KEY BLOCK- msg04571/pgp0.pgp Description: PGP signature
