I have two CentOS 5 servers with nearly identical specs. When I login and do
ulimit -u, on one machine I get
unlimited, and on the other I get
When I run a cron like:
* * * * * ulimit -u > ulimit.txt
I get the same results (
I am trying to determine where these are set so that I can alter them. They are not set in any of my profiles (
/etc/profile, etc.). These wouldn't affect cron anyway) nor in
/etc/security/limits.conf (which is empty).
I have scoured google and even gone so far as to do
grep -Ir 77824 /, but nothing has turned up so far. I don't understand how these machines could have come preset with different limits.
I am actually wondering not for these machines, but for a different (CentOS 6) machine which has a limit of
1024, which is far too small. I need to run cron jobs with a higher limit and the only way I know how to set that is in the cron job itself. That's ok, but I'd rather set it system wide so it's not as hacky.
Thanks for any help. This seems like it should be easy (NOT).
EDIT -- SOLVED
Ok, I figured this out. It seems to be an issue either with CentOS 6 or perhaps my machine configuration. On the CentOS 5 configuration, I can set in
* - nproc unlimited
and that would effectively update the accounts and cron limits. However, this does not work in my CentOS 6 box. Instead, I must do:
myname1 - nproc unlimited myname2 - nproc unlimited ...
And things work as expected. Maybe the UID specification works to, but the wildcard (*) definitely DOES NOT here. Oddly, wildcards DO work for the
I still would love to know where the default values are actually coming from, because by default, this file is empty and I couldn't see why I had different defaults for the two CentOS boxes, which had identical hardware and were from the same provider.