Tag Info

New answers tagged

0

Process limits are controled by setrlimit(2) So you can look into its manpage: RLIMIT_SIGPENDING (Since Linux 2.6.8) Specifies the limit on the number of signals that may be queued for the real user ID of the calling process. Both standard and real-time signals are counted for the purpose of checking this limit. However, the limit is ...


0

Do you have an /etc/pam.d/su? On some systems, such as Debian Squeeze (at least), processing of limits configuration is disabled for su. For example, inside /etc/pam.d/su, you may see something like this: # Sets up user limits, please uncomment and read /etc/security/limits.conf # to enable this functionality. # (Replaces the use of /etc/limits in old ...


0

Rather than manually running ./script.sh stop;./catalina.sh start and separately having a cronjob that does the same, use an /etc/init.d/catalina script that can configure all your limits, env vars, etc; then to start/stop, just run sudo /etc/init.d/catalina start (or stop, restart, etc); or, more simply (if available) sudo service catalina start (etc). It's ...


1

Only root can raise the current hard limit. Presumably the default limit for that user as set in /etc/security/limits.conf is 16384, but there is something in an initialization file that sets the limit to 4096. If you can, change this initialization file to set only the soft limit. The soft limit can be changed in either direction at any time by any user, ...



Top 50 recent answers are included