diff options
| author | varac <varacanero@zeromail.org> | 2016-05-12 13:59:13 +0200 |
|---|---|---|
| committer | varac <varacanero@zeromail.org> | 2016-05-12 13:59:13 +0200 |
| commit | e35fca3d367a6294123a0d9a2c077f4db7dfe809 (patch) | |
| tree | 1c7f1c85561ce5fd91f731659b5c2b3039593821 /puppet/modules/rubygems/manifests/xmpp4r.pp | |
| parent | e71c10af73be758e407ee352a3a7b12347177dce (diff) | |
[feat] catch abnormal proc termination in syslog
Sometimes a floating point exception or segfault of
a process results in systemd restarting it, we want
to recognize this from the syslog
i.e.:
systemd[1]: pixelated-server.service: main process exited,
code=killed, status=8/FPE
systemd[1]: Unit pixelated-server.service entered failed state.
- Related: https://github.com/pixelated/pixelated-user-agent/issues/683
Diffstat (limited to 'puppet/modules/rubygems/manifests/xmpp4r.pp')
0 files changed, 0 insertions, 0 deletions