CPU control

This project is for a hosting company in need of tools to automate and control the CPU usage of the web servers. Problem: I put about 100 sites on a celeron 2.4. I want the CPU load avrage to always stay under 1.00 - right now, any proccess can overload the server CPU at any time: php, exim, httpd, mysql, perl, phyton, spamd etc etc Solution: ·Monitor the CPU load ·Creates load statistics ·Alert when CPU load is above a certain adjustable value Reaction: Termination of any PID occupying CPU on a percentage of ___ for a length of time of ­__ Restart of specific services (limited to minimum time lapses and daily quotas of ___) if CPU maintains a high load volume of ____ for a period as long as ____ Log PID user, reseller, time, process, etc Automatic server reboot if CPU maintains a high load volume of ____ for a period as long as ____ Notification to NOC on each phase, maximum alert if automated escalation reaches __ Reseller CPU usage control: Log the daily, weekly, monthly CPU usage of each reseller Show the space, bandwidth, CPU usage + statistics in a raw output to a log file (for future gui/frontend functionality. gui/frontend is not part of this project) => Duration of project: 7 days for development, 14 days of performance observation, testing, debugging and updates. => During the entire duration of this project, the coder will be responsible to monitor and control the CPU load during 12 hours of the day. The 12 hours are 9 am to 9 pm EST on all days. the other 12 hours would be optional but highly recommended in order to get a maximum of real life samples of CPU overload scenarios. => If we want to initiate a helpdesk communication with the coder at any time during this project, we must be able to get a response within 90 minutes for regular communication and 15 minutes for an emergency. => The project will be considered complete only once the CPU daemon has worked flawlessly for 14 days after its completion. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Unix Linux Hosting ModernBill