Systemd is trying to stop a service. To do an action to a service (or any unit), it runs a job. The job to stop a service is called a stop job. Once the stop job is taken off the job queue, the stop job is running.
The method of stopping a service is configurable, but the default is to send a kill signal to the MainPID, then wait for the process to exit. If it doesn’t, after a timeout, the kill is reattempted with a harsher signal.
You’re welcome.
OH LOOK A CONF FILE TO EDIT.
Full circle, bitches.
What the fuck it even means for a stop job to run?
Systemd is trying to stop a service. To do an action to a service (or any unit), it runs a job. The job to stop a service is called a stop job. Once the stop job is taken off the job queue, the stop job is running.
The method of stopping a service is configurable, but the default is to send a kill signal to the MainPID, then wait for the process to exit. If it doesn’t, after a timeout, the kill is reattempted with a harsher signal.
So its the units to blame
What is the default of the default?
Dunno, but looks at
man service.unitI think)Type
rebootinto an SSH session and play everyone’s favorite game show…WILL IT ACTUALLY DO IIIIIIIIIIIIIIT