I didn't realise that there was already a duplicate of this until I read it.
The proposed way to do this is through custom actions, rather than directly naming the signal in initctl (thus a job would define the signals it wants to receive, and give them more descriptive names)
I didn't realise that there was already a duplicate of this until I read it.
The proposed way to do this is through custom actions, rather than directly naming the signal in initctl (thus a job would define the signals it wants to receive, and give them more descriptive names)