If you are talking about the ulimit values, most are set to unlimited: [EMAIL PROTECTED] ~]# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited pending signals (-i) 1024 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 71680 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
BTW, this is a x64 install. ---------------------------------------------------- Zoltan Forray Virginia Commonwealth University Office of Technology Services University Computing Center e-mail: [EMAIL PROTECTED] voice: 804-828-4807 Richard Sims <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[email protected]> 06/05/2007 03:03 PM Please respond to "ADSM: Dist Stor Manager" <[email protected]> To [email protected] cc Subject Re: [ADSM-L] New Linux server issues On Jun 5, 2007, at 2:44 PM, Zoltan Forray/AC/VCU wrote: > I see a lot of these message are related to memory. This box has > 8GB or > RAM. One would think that was enough. Zoltan - That's a physical resource. But what about the Unix Resource Limits which may have been in effect when the server process started, and could artificially limit what the process may use? Your posting doesn't mention that factor, so something worth checking. Richard Sims
