[SOLVED] cron jobs not using ulimit set in .bashrc

Iyyappan · 12-20-2013, 12:32 AM

Hi,
We have two Red Hat Enterprise Linux Server release 5.10 (Tikanga) servers. ulimit -HSN 16834 is set in .bashrc for root in both the servers. script to display to ulimits gives 1024 in one server and 16834 in another server..... Limits are not set currently in limits.conf..... Apart from .bashrc, ulimit -HSN 16834 is not set in any other file....

Shall I set the entries in crontab n check?

cat /etc/pam.d/login
#%PAM-1.0
auth [user_unknown=ignore success=ok ignore=ignore default=bad] pam_securetty.so
auth include system-auth
account required pam_nologin.so
account include system-auth
password include system-auth
# pam_selinux.so close should be the first session rule
session required pam_selinux.so close
session optional pam_keyinit.so force revoke
session required pam_loginuid.so
session include system-auth
session optional pam_console.so
# pam_selinux.so open should only be followed by sessions to be executed in the user context
session required pam_selinux.so open

berndbausch · 12-20-2013, 07:05 PM

bashrc is for an interactive shell. From the man page (I added the highlight):

Quote:

When an interactive shell that is not a login shell is started, bash reads and executes commands from ~/.bashrc, if that file exists. This may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of ~/.bashrc.

When bash is started non-interactively, to run a shell script, for example, it looks for the variable BASH_ENV in the environment, expands its value if it appears there, and uses the expanded value as the name of a file to read and execute. Bash behaves as if the following command were executed:

if [ -n "$BASH_ENV" ]; then . "$BASH_ENV"; fi
but the value of the PATH variable is not used to search for the file name.

So one solution would be to set BASH_ENV in your crontab.

Iyyappan · 12-30-2013, 10:59 PM

ISsue was with open file limit settings....... added source /etc/profile in script starting..

astrogeek · 12-30-2013, 11:08 PM

CRON jobs do not run in a login shell and have no knowledge of what might be in .bashrc.