Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've recently moved from IRIX to Linux (SUSE) and found the default job scheduler (at or batch, via atd) to be woefully inadequate. The IRIX "at" and "batch" used cron and a queue definition (queuedefs) that worked pretty well at throttling background processes.
I am familiar with cron and use it extensively to run regularly scheduled scripts. I'm talking about a slightly different situation than that. We have an application that submits jobs (bash shell scripts that mainly run reports) on demand via the "batch" command. On IRIX, this was basically an extension of cron, with the added ability to throttle the number of jobs simultaneous running, as well as the priority, aka nice. Since the jobs were submitted by multiple users in an uncoordinated way, it gave me the ability to control how many process ran in the background. I could open it up as wide as I wanted or shut it down completely. The Linux implementation works slightly different. Instead of explicitly controlling the number of jobs, it uses system load average. That is too simplistic, as there are other resource choke points than cpu utilization.
With all that being said. I was hoping that someone had experience with some of the open source job schedulers out there. In other words I was hoping to learn from someone else's pain as to what works and what doesn't.
Does anyone have a suggestion on a job, or process, scheduler for Linux?
Last edited by mrbarritt; 09-27-2010 at 02:34 PM.
Unlike Unix, on Linux loadavg is not just the runqueue. It incorporates tasks in uninterruptable sleep. Usually tasks waiting (disk) I/O, but not necessarily - children can be marked uninterruptable sleep as well - hopefully for (very) short periods. So I guess the concept is to allow a system managed control rather than the admin having to monitor it.
Not saying it's great (as I don't use it), but is likely to be more dynamic than you appear to crediting it.