查看/var/log/secure这个日志的时候,发现了一些错误日志:
Jul 29 00:00:01 clang crond[14116]: pam_limits(crond:session): unknown limit item 'noproc' Jul 29 00:00:01 clang crond[14116]: pam_limits(crond:session): unknown limit item 'noproc' Jul 29 00:00:01 clang crond[14116]: pam_limits(crond:session): unknown limit item 'noproc' Jul 29 00:01:01 clang crond[14130]: pam_limits(crond:session): unknown limit item 'noproc' Jul 29 00:01:01 clang crond[14130]: pam_limits(crond:session): unknown limit item 'noproc' ......
“unknown limit item ‘noproc”意思是未知的限制单位,看样子是关于limit session的,就是限制对话数的最大上限。查了一下资料,这东西归/etc/security/limits.conf这个配置文件管的,打开看了一下,里面有配置说明
#<item> can be one of the following: # - core - limits the core file size (KB) # - data - max data size (KB) # - fsize - maximum filesize (KB) # - memlock - max locked-in-memory address space (KB) # - nofile - max number of open files # - rss - max resident set size (KB) # - stack - max stack size (KB) # - cpu - max CPU time (MIN) # - nproc - max number of processes # - as - address space limit (KB) # - maxlogins - max number of logins for this user # - maxsyslogins - max number of logins on the system # - priority - the priority to run user process with # - locks - max number of file locks the user can hold # - sigpending - max number of pending signals # - msgqueue - max memory used by POSIX message queues (bytes) # - nice - max nice priority allowed to raise to values: [-20, 19] # - rtprio - max realtime priority
看到高亮的部分没,是不是和我们的出错的信息”noproc“这东西很像,应该它就是罪魁祸首了。再往下看这个配置文件
# End of file * soft noproc 65535 * hard noproc 65535 * soft nofile 65535 * hard nofile 65535
应该把noproc改成nproc,意思就是最大的进程数(对话数)。