Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
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.
Questions:
1) How do you enable any user to have the “sysops” privilege to increase ulimit settings?
2) or, How do you affect the default file handle (descriptor) limit?
As it stands, every session begins with the default limit of 1024, and only root can up the limit (ex: ulimit -n 8192). I’ve attempted to add users to the root group (only as a test) but that doesn’t allow them to up the limit.
I have tried everything (I think), except for a kernel rebuild (which shouldn't have to be performed for this!), to affect the default file handle maximum:
1) /etc/security/limits.conf
2) /etc/pam.d/login
3) /etc/profile
4) a users individual .profile
5) /proc/sys/fs/files-max
Any suggestions?
Many Thanks,
Rob
Forgot to add that in addition to using ksh, the userid's in question are not local accounts, but are obtained from yp services...however, I tested creating a local account and still the same behavior...
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
I *believe* the only option you have is to change it in the code and
recompile. root can raise the hard limit for root, but not for anyone
else. This is stupid (in my opinion), it should at least allow root to
change it for a given uid.
Moses...thanks. I too believe that a recompile is the only way too. Agree with your opinion re: the ulimit call being limited as it is. What's funny is that RHAS is targeted for high availability / scalability / throughput environments but apparently someone believes that the processes supporting the environment are to be run as root? In the environments I routinely run in, I'll hit the file descriptor and other default limits very quickly. True, not too many kernels are tuned out-of-the-box for large scale / clustered environments, but the parameters I am dealing with at this point are very rudementary.
Anyway, enough of my diatribe...thanks again for the response...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.