limiting simultaneous batch streams on Linux server
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
limiting simultaneous batch streams on Linux server
Linux does not provide a way to constrain the number of concurrent batch processes (jobs submitted via "at"). I need to limit these processes because our interactive booking environment is being impacted when too many jobs are running simultaneously in batch.
Is there and add-on solution someone can recommend to do this on RHEL 5.6?
Thanks, but CPU load is not my issue - it is file contention when too many batch processes are run at the same time.
I need to limit the number of batch streams that are open.
Are the at jobs being run all using the same script/binary? If it is a script you could modify the script itself to defer its run if it sees so many other copies already running. If it is a binary you could write a wrapper script to do that. It sounds to me as if your issue is not the number of at jobs per se but rather the number of copies of the same program running kicked off by at.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.