Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
memory limit per process
- Thread starter nyck
- Start date
RMGBELGIUM
MIS
this can be done through the ulimit command ( ulimit -m )
rgds,
R.
rgds,
R.
Hi,
if you enter vi /etc/security/limits
you can see the file organization and modify
default or for a specific user the value:
memory, stack, rss giving also a -1 value.
This can resolve your problem, knowing that if is a
server with large number of interactive users
(developper also) you can lead at unpredictable
result, while if it is a workstation box or
a system in which you are the only user, this is the
standard. If it is a DB server or other specific
application server, look for application Producer
(e.g. Oracle) indications.
I suggest to don't unlimit the number of opened files
(nofiles), becouse some applications uses this number
and fails to understand the -1 valu as unlimited.
If you are not a developper and you don't need to evaluate core files (or send them to other to evaluate) don't unlimit
core value, rather decrease it, in way that when a program crashes, the core file does not fill your filesystem.
The value fsize is another field that you can need to increase or unlimit.
While you modify the /etc/security/limit in a window with root authority (without exiting, but just saving file by :w), in anoter windows perform "login youruser" and giving the command "ulimit -a" see the effect that you
produce modifying and saving the security file
ciao
vittorio
if you enter vi /etc/security/limits
you can see the file organization and modify
default or for a specific user the value:
memory, stack, rss giving also a -1 value.
This can resolve your problem, knowing that if is a
server with large number of interactive users
(developper also) you can lead at unpredictable
result, while if it is a workstation box or
a system in which you are the only user, this is the
standard. If it is a DB server or other specific
application server, look for application Producer
(e.g. Oracle) indications.
I suggest to don't unlimit the number of opened files
(nofiles), becouse some applications uses this number
and fails to understand the -1 valu as unlimited.
If you are not a developper and you don't need to evaluate core files (or send them to other to evaluate) don't unlimit
core value, rather decrease it, in way that when a program crashes, the core file does not fill your filesystem.
The value fsize is another field that you can need to increase or unlimit.
While you modify the /etc/security/limit in a window with root authority (without exiting, but just saving file by :w), in anoter windows perform "login youruser" and giving the command "ulimit -a" see the effect that you
produce modifying and saving the security file
ciao
vittorio
- Status