I am finding that the service module in the core ansible modules does not work for starting/stopping services on a Slackware system. Slackware, as you might know, does not use the same startup script systems that most Linux distributions use. It uses something much more BSD like, but not exactly like either.
I’m wanting to know if there is a known work-around for this. I am considering a hack to the service module code, but I didn’t want to do that if there was some known good solution.
It uses a rc.d system which is what berkely/BSDs use, unlike most linux that use a sysV init system. I would create a specific module and then add ‘init system discovery’ to set to that in fact gathering.
Interesting suggestion. What I have done so far is I have added some code to the service.py module. That module already looks for a bunch of different kinds of service management systems for a number of different operating systems. I have it working pretty well. Once I have used it enough to feel that it is fairly bug free, I would be happy to contribute it.
I’m in the process of deprecating service module just because of what you state, it is very prone to error and breaking and does not support all those systems well. Also it limits the options and behaviors available.