This isn't exactly what I want to do. According to the FreeBSD Handbook, by
defining a CPU limit it will just kill any process that uses more than the
limit. What I want to do is effectively throttle the process so it doesn't
use up more than a certain % CPU, but still lives, esentially taking longer
to process than if it had unlimited resources. That way the process still
runs and the system isn't taken to it's knees.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill Moran
Sent: Thursday, April 12, 2007 1:32 PM
To: Don O'Neil
Cc: [EMAIL PROTECTED]
Subject: Re: Mysql Hogging all system resources

In response to "Don O'Neil" <[EMAIL PROTECTED]>:

> I have a customer that loaded up a HUGE table and was doing all sorts 
> of fancy stuff in it, and not waiting for the process to finish before 
> sending the same query, and eventually loading up the server to the 
> point where the only thing I could do was unplug it.
> 
> Is there a way to prioritize or set the amount of resources that MySQL 
> is allowed to have? Do I need to set it up as a jailed process maybe? 
> I've never done that before, so I'm not sure if it's the right approach or
not.

man login.conf should tell you all you need to know.

--
Bill Moran
http://www.potentialtech.com
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to