Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
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.
that looks reasonable, but I don't know what loads you have.
can users do "sudo -i" ?
I suspect your max openfiles per user is 4096, root currently has 1736
if you have a number of root shells open, you could end up hitting that 4096 limit, thus the shell won't open ( no resources )
if you experience problems 'more often than not' , then look at
No, the users can't run sudo -i, but if i run this command, the error message changes, in this case the error message is : enable to execute /bin/bash, not /bin/su
Your "max user processes" and "open files" look really really low:
Quote:
Originally Posted by ruffrider
Code:
As user is :
core file size (blocks, -c) 200000
data seg size (kbytes, -d) 200000
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 256637
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) 200000
open files (-n) 100
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 35
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Compare yours above to mine below. I am running a standard install of LinuxMint, what you see below are the defaults:
Code:
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 26940
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 26940
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
And sitting here, running no user processes on my computer other than the Xfce desktop, the Firefox browser I am typing in right now, and a single terminal window, I am already running 46 processes. Even that is above your limit of 35:
Code:
$ ps -ef | grep my_login_id | wc -l
46
I believe your extremely low settings for user open files and max processes is what is killing you. Why do you have these parameters set so low? IMHO, these settings are so low as to be almost unuseable.
I think they should spend a bit more time reviewing the limits they came up with then.
35 processes is extremely low, even for commandline only users with no GUI, unless those users do basically nothing but sit there and stare at their command prompt. I could live with an open file limit of 100 however, assuming these users are not running production processes, servers, etc.
It is good to set user limits on a production system. It is bad to set those limits unrealistically low.
Anyway, the issue here is not good or bad practice by sysadmins. It is the failure to invoke sudo for this specific userid. No doubt that is because of the low user max process limit, as evidenced by "Resource temporarily unavailable".
O.P. - Get the sysadmin to up your user max process limit and I'll bet that error goes away. Alternately, kill some of the processes you are currently running to make room for more. You will need to kill more than one of your excess processes, because "sudo su -" will try to start up a handful of processes, not just one.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.