jobs: Abort when systemd's event loop lost 67/16267/1 5.99.4 flounder/5.99.4 flounder_5.99.4
authorJosé Bollo <jose.bollo@iot.bzh>
Thu, 23 Aug 2018 10:23:39 +0000 (12:23 +0200)
committerJosé Bollo <jose.bollo@iot.bzh>
Thu, 23 Aug 2018 10:42:14 +0000 (12:42 +0200)
commit8aac4b82fa18fe6f0feacac86fdde3d78b19cd18
tree51075bc3b4f4ff68cbd1717934900b502da1a186
parent2991a2564bc5e21b04dcb3157ce38804080c0056
jobs: Abort when systemd's event loop lost

When sd_event_prepare returns an error there is currently
no way to restore the event loop working.

It happens when a callback of an sd_event is faulty
(ex: SIGSEGV). In that case the monitoring of signals
(sig-monitor) interfer badly with systemd. But at the
the application firstly has error.

To avoid flooding the journal with messages, aborting
is the best solution.

Bug-AGL: SPEC-1681

Change-Id: If01295f07b3c3fc8c8ec1ac5bf04840d42ee9774
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
src/jobs.c