When using a personal computer, it can be easy to determine when a job is caught

Question

When using a personal computer, it can be easy to determine when a job is caught in an infinite loop or system-wide freeze. The typical solution to this problem is for the user to manually intervene and terminate the offending job, or in the worst case, all jobs. What mechanism would you implement in the Process Scheduler to automate the termination of a job that’s in an infinite loop? Take into account jobs that legitimately use large amounts of CPU time, such as a task that is calculating the first 300,000 prime numbers.

Explanation / Answer

For this typical solution, we can set time and resource both to the CPU, which is compared to the accrued CPU time of each job. Each classification screens to ensure that maximum resources for that class are not exceeded, and does not permit the job to run longer than the maximum time allowed .If a job's accrued CPU time is equal to (or exceeds) this maximum then it is terminated. we can also provide a time estimate required when the job is submitted. Terminate the job when the job estimated time or job class time is exceeded. Maintain statistics on the CPU time used per account. Whenever a job exceeds 2 standard deviations from the average time used, place the job on hold until the user is contacted.For the interactive user who uses lots of CPU time, check the customer profile. Check on system security issues, such as file accesses, privileged instructions uses etc.

Related Questions

Navigate

• Browse (All)
• Browse W
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.