今日闲来无事,就看群里大佬吹牛逼了,偶然一条技术疑问提出来了,神奇啊,作为广大老司机技术交流群体竟然还有这么深入的研究?
大佬问:这个文件句柄限制怎么设置了/etc/security/limits.conf对进程都无效呢?如图
刚好看到了这方面的知识点,在修改/etc/security/limits.conf以及使用ulimit -n命令进行修改文件句柄数量时,是需要重新进入终端方可生效的,于是饶有兴趣地告诉大佬:重开终端吧!
大佬又回了一句:我服务器都重启了一遍了,就是不生效!!!
疑问来了,这是为什么呢?????于是,自我实践验证修改,哎哟.......还真不生效。如下一顿操作猛如虎:
[root@jenkins ~]# 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) 3851
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) 3851
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
[root@jenkins ~]# vim /etc/security/limits.conf
[root@jenkins ~]# ulimit -n 65535
[root@jenkins ~]# 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) 3851
max locked memory (