|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
praiskup commented 7 years ago | ||
clime commented 7 years ago It is not needed but with this the service shows as active (exited). (without it shows as inactive (dead) after it has been successufully run). Also, this setting is recommended to use with "Type=oneshot". | ||
praiskup commented 7 years ago Ah, thanks for the info. | ||
|
||
|
||
|
||
This pull request enables a COPR admin to start/stop COPR components individually. This might be useful for error recovery in case some component stops functioning properly. COPR components currently include: copr-backend-action (Action dispatcher), copr-backend-build (Build dispatcher), copr-backend-log (Redis Log handler), and copr-backend-vmm (Virtual Machine manager).
Is this RemainAfterExit statement really needed?