On Tuesday 31 January 2006 16:02, Shlomo Solomon wrote: > I'm answering my own post, but since I found the problem, I thought it > might help others who might come accross the same situation.
> > 1 - Who or what is killing X and why is 3.51% a high enough load to > > decide to kill X? BTW - thie pecentage varies and is sometimes very high, > > but usually not. > > When installing MDV2006, I chose "tons" of packages. It seems that one of > them was something called "loadcontroller" and aside from the fact that > this is BETA software, it seems to work with very wierd logic. Actually, it makes perfect sense if you run a server. You want to kill processes that are killing your performance (maybe because they were exploited?) and you want to get notified when that happens. Load controller offers that functionality. Although beta quality, and extremely lacking on the documentation side, it has proven valuable to me. > It > periodically checks CPU usage and if you're over a certain level (the > default is 5%), Please note - the "5" in the configuration of that parameter is not "5 percent" , but a load average of 5 (as clearly specified in the comments - what you get when you run uptime), which means 500% of CPU usage (virtually, anyway). > it kills the "heaviest" CPU user - even if that application > is not really using very much CPU. Or anything which is over "USAGELIMIT" which is set by default to 25 (this time it is percent of actual CPU usage). I changed it to 50. Also, your analysis (which I snipped, sorry) is a bit off because of the values you specify. specifically loadcontroller will kill the worst offender, regardless of what else is running which will under most cases is what you want. The only major problem I see with this approach is that a lot of times, your worst offender is killing your machine with I/O and not CPU usage, which can't be detected by loadcontroller (nor by any other means I know of, under Linux) and thus loadcontroller might well kill an innocent victim. This haven't happened to me ever since I change hardware to something with a bit more bandwidth, but if your system is I/O bound (like most not-top-of-the-line consumer PCs which run X and something useful over it) then by all means, do disable loadcontroller. > > 2 - I don't know why these e-mails are being sent to > > [EMAIL PROTECTED] instead of [EMAIL PROTECTED] and get > > This address is "hard-coded" in the loadcontroller configuration file. Hardcoded only in the sense of being a default setting in a configuration file which you are expected to edit. Noteably this default is probably set incorrectly and the loadcontroller packager should be notified to change it to [EMAIL PROTECTED] or just simply root. -- Oded ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
