Linux環境下進程發生異常而掛掉,通常很難查找原因,但是一般Linux內核給我們提供的核心文件,記錄了進程在崩潰時候的信息,在C語言類的大型項目中,有助于深入定位。其配置流程如下:
1 查看生成core文件開關是否開啟 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) 2061196
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1048576
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) 1048576
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
2 ulimit -c [kbytes]可以設置系統允許生成的core文件大小;
ulimit -c unlimited // 不限制core文件的大小core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 2061406
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 524288
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) 131072
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
上述方式不是永久生效的,要使其永久生效,可以進行如下設置
1 vi /etc/security/limits.d/20-nproc.conf
* soft nproc unlimited
root soft nproc unlimited
postgres soft core unlimited
postgres hard core unlimited
2 指定core文件的名字與生成路徑
執行# vim /etc/sysctl.conf,進入編輯模式,加入下面兩行
kernel.core_pattern=/var/core/core_%e_%p
kernel.core_uses_pid=0注釋: %e dump文件名 %p 進程號
3 執行sysctl -p /etc/sysctl.conf,使其修生效。
參考:https://blog.csdn.net/luronggui/article/details/128728235