-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi Sam, can you check your /etc/pam.d/sshd and look for a line like this: session required pam_limits.so if that is the case, you can check also the limits applied by PAM here: /etc/security/limits.conf HTH, - -Nik Sam Przyswa wrote: > Nikolay Kichukov a écrit : >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi, >> did you check your pam limits for ssh login? >> > I got this: > > zimbra:~# ulimit -a > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 16382 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 1024 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) unlimited > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited > > Sam. > > >> Sam Przyswa wrote: >> >>> Daniel Hokka Zakrisson a écrit : >>> >>>> Sam Przyswa wrote: >>>> >>>> >>>>> Nikolay Kichukov a écrit : >>>>> >>>>>> hi, >>>>>> the correct place would be: >>>>>> /etc/vservers/<server-name>/rlimits/nofile >>>>>> >>>>>> >>>>> Thanks, when I check I got: >>>>> >>>>> vserver-1:~# cat /proc/virtual/40000/limit >>>>> Limit current min/max soft/hard hits >>>>> PROC: 53 0/ 112 -1/ -1 0 >>>>> VM: 576741 0/ 1431259 -1/ -1 0 >>>>> VML: 0 0/ 0 -1/ -1 0 >>>>> RSS: 64550 0/ 96015 -1/ -1 0 >>>>> ANON: 54704 0/ 83032 -1/ -1 0 >>>>> RMAP: 9846 0/ 18778 -1/ -1 0 >>>>> FILES: 489 0/ 662 65535/ 65535 0 >>>>> OFD: 203 0/ 203 -1/ -1 0 >>>>> LOCKS: 16 0/ 20 -1/ -1 0 >>>>> SOCK: 19 0/ 19 -1/ -1 0 >>>>> MSGQ: 0 0/ 0 -1/ -1 0 >>>>> SHM: 0 0/ 0 -1/ -1 0 >>>>> SEMA: 0 0/ 0 -1/ -1 0 >>>>> SEMS: 0 0/ 0 -1/ -1 0 >>>>> DENT: 631 0/ 722 -1/ -1 0 >>>>> >>>>> But the ulimit -a give: >>>>> >>>>> zimbra:~# ulimit -a >>>>> core file size (blocks, -c) 0 >>>>> data seg size (kbytes, -d) unlimited >>>>> scheduling priority (-e) 0 >>>>> file size (blocks, -f) unlimited >>>>> pending signals (-i) 16382 >>>>> max locked memory (kbytes, -l) 64 >>>>> max memory size (kbytes, -m) unlimited >>>>> open files (-n) 1024 >>>>> pipe size (512 bytes, -p) 8 >>>>> POSIX message queues (bytes, -q) 819200 >>>>> real-time priority (-r) 0 >>>>> stack size (kbytes, -s) 8192 >>>>> cpu time (seconds, -t) unlimited >>>>> max user processes (-u) unlimited >>>>> virtual memory (kbytes, -v) unlimited >>>>> file locks (-x) unlimited >>>>> >>>>> As it's limit at 1024 as well as the vserver host. >>>>> >>>>> Is it right ? >>>>> >>>> ulimits and rlimits are not the same. rlimits apply to the entire >>>> guest, >>>> ulimits apply to the process. Change >>>> /etc/vservers/<guest>/ulimits/nofile >>>> as well to alter the ulimit value. >>>> >>> Ok but this doesn't change I always have ulimit -n 1024 but the >>> ulimits/nofile is 524288 >>> >>> Curiously when connect the guest with command "vserver guest enter" the >>> ulimit -n give 524288 but if I connect by SSH on guest the ulimit -n >>> give 1024 and I can't set the ulimit by command "ulimit -n 524288" that >>> give me operation denied !? >>> >>> I use 2.6.26-2-vserver-686-bigmem on Debian squeeze/sid >>> >>> Sam. >>> >>> > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEcBAEBAgAGBQJL6o9FAAoJEDFLYVOGGjgXBqMIAMmWN1cbfIXZPBMsX7k1W+GF bDOugjBMqhFgfiO3I5PUqf7Vt7QVPNK9Mz6LOyXIZasMAFuhgReB/yZTDvIUfpyx gcEbZyDMqIXTiCAR/Ehyaf2BX/3osFeEqIRDWIPHpaN+tV21SM1poxjUF8XSGAlC xS+ImLpHeOgpIN4i6wh8FaaIW62X0QHArnFrMZQDvv0luaocSFWbKbmCsDGK3M6F WTNmVURi4dwBcNsskfvj/hfIKLOMXsh+5tnMRtt2hJIIGbQB1lqzLeeNxhXKs4mn 2BbluCfunhz/LsKq6H8DYBjNkozIJq33Ay6uVOvsVKEzR54I3icQ3GoLTySAWGc= =udIo -----END PGP SIGNATURE-----