Ticket 4321

Summary: Add option RemainAfterExit=no in systemd files
Product: Slurm Reporter: Mathis Clayer <mathis.clayer>
Component: OtherAssignee: Felip Moll <felip.moll>
Status: RESOLVED INVALID QA Contact:
Severity: 4 - Minor Issue    
Priority: --- CC: felip.moll, thomas.cadeau
Version: 17.11.x   
Hardware: Linux   
OS: Linux   
Site: Atos/Eviden Sites Alineos Sites: ---
Atos/Eviden Sites: Grenoble Confidential Site: ---
Coreweave sites: --- Cray Sites: ---
DS9 clusters: --- HPCnow Sites: ---
HPE Sites: --- IBM Sites: ---
NOAA SIte: --- OCF Sites: ---
Recursion Pharma Sites: --- SFW Sites: ---
SNIC sites: --- Linux Distro: ---
Machine Name: CLE Version:
Version Fixed: Target Release: ---
DevPrio: --- Emory-Cloud Sites: ---
Attachments: Add option RemainAfterExit=no in systemd files

Description Mathis Clayer 2017-10-31 09:27:25 MDT 
Created attachment 5472 [details]
Add option RemainAfterExit=no in systemd files

RemainAfterExit=
       Takes a boolean value that specifies whether the service shall be considered active even when all its processes exited. Defaults to no.

By switching between systemctl start slurmd or other service, and the command slurmd, the deamon could by seen as active for systemd with no process running.
Comment 1 Felip Moll 2017-10-31 10:54:12 MDT 
Hello Mathis,

I don't see the point of adding this option if it defaults to 'no'.

Could you elaborate a little bit more?

Thanks,
Felip M
Comment 2 Felip Moll 2017-11-07 06:02:02 MST 
Hi Mathis,

I am marking this bug as TIMEDOUT since we did not get a response within a week and I need more information to confirm this problem.

Open this bug again if you want to continue with it.

Best regards,
Felip M
Comment 3 Mathis Clayer 2018-01-17 03:07:32 MST 
Hi,

You're right, there is no reason for adding this option.


Best regards.

Mathis C.
Comment 4 Felip Moll 2018-01-17 06:55:31 MST 
Ok, marking as invalid then.