Home
DevCentral
Search
Configure Global Search
Log In
Transactions
T1213
Change Details
Change Details
Old
New
Diff
We've seen this on IRC: 18:45:46 -!- Odderon [odderon@eglide.org] has quit [Quit: Caught SIG_SEGV! Aborting connection. Uptime: 893 hours, 10 mins] Then, it didn't restart. ```name=Eglide $ systemctl status odderon ● odderon.service - Odderon darkbot Loaded: loaded (/etc/systemd/system/odderon.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Sat 2017-06-03 18:45:46 UTC; 2min 35s ago Main PID: 6397 (code=killed, signal=QUIT) ``` According to https://www.freedesktop.org/software/systemd/man/systemd.service.html#Restart= the `Restart` parameter controls the restart behavior, with `on-failure` the option to allow to restart when the process exits with a non 0 ("unclean" in the doc) exit code.
We've seen this on IRC: 18:45:46 -!- Odderon [odderon@eglide.org] has quit [Quit: Caught SIG_SEGV! Aborting connection. Uptime: 893 hours, 10 mins] Then, it didn't restart. ```name=Eglide $ systemctl status odderon ● odderon.service - Odderon darkbot Loaded: loaded (/etc/systemd/system/odderon.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Sat 2017-06-03 18:45:46 UTC; 2min 35s ago Main PID: 6397 (code=killed, signal=QUIT) ``` According to https://www.freedesktop.org/software/systemd/man/systemd.service.html#Restart= the `Restart` parameter controls the restart behavior, with `on-failure` the option to allow to restart when the process exits with a non 0 ("unclean" in the doc) exit code.
Continue