ulimit详解（国外英文资料）.doc

ulimit详解（国外英文资料） This is a very good article for the ulimit of Linux on the 11-24 10:46, which is a very good article about the limitations of ulimit. The original link: /home-space-uid-56821-do-blog-id-232810.html You can generally use the ulimit command or edit /etc/securi/in.conf to reload the method The ulimit is more direct, but only in the current session, and the limit.conf can be used in the next login, based on users and restrictions. The setting of the in.conf is done through the load of pam_limits. So, such as /etc/pam. D/SSHD, which loads the limit by SSH login. Or the /etc/pam. D/login load takes effect. The restrictions are analyzed below The core file size (blocks, -c) 0 Data seg size (kbytes, -d) unlimited Scheduling priority (-e) 20 a File size (blocks, -f) unlimited a Pending signals (-i) 16382 Max locked memory (kbytes, -l) 64 a Max memory size (kbytes, -m) unlimited a Open files (-n) 1024 a Pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 Real time priority (-r) 0 Stack size (kbytes, -s) 8192 CPU time (-t) unlimited Max user processes (-u) unlimited Virtual memory (kbytes, -v) unlimited File locks (-x) unlimited (1) limit the amount of file size (file size) generated by the process Lets start with the hard and soft limits of ulimit Hard limit the -h parameter, soft limit the -s parameter. Ulimit - a sees a soft limit, which you can see through ulimit-a-h. If the ulimit doesnt limit the use of -h or -s, its going to change both classes at the same time. The soft limit can limit the user/groups use of resources, and the hard limit is to control the soft limit. Both the superuser and the average user can expand the hard limit, but the superuser can narrow the hard limit, and the average user cant narrow the hard limit. When a hard limit is set, the set of soft limits can only be less than or equal to the hard limit. The following tests apply to hard and soft limits. 1) soft limits should not exceed hard limits Under the super user