# service module with Slackware

**URL:** <https://forum.ansible.com/t/service-module-with-slackware/23220>\
**Category:** Ansible Project\
**Created:** [December 9, 2016, 9:01pm UTC](https://forum.ansible.com/t/service-module-with-slackware/23220 "2016-12-09T21:01:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Steve\_Saner](https://avatars.discourse-cdn.com/v4/letter/s/43a26b/32.png) [@Steve\_Saner](https://forum.ansible.com/u/Steve_Saner)\
**Post date:** [December 9, 2016, 9:01pm UTC](https://forum.ansible.com/t/service-module-with-slackware/23220/1 "2016-12-09T21:01:41Z")

</div>

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.

Thanks

Steve

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [December 14, 2016, 9:47pm UTC](https://forum.ansible.com/t/service-module-with-slackware/23220/2 "2016-12-14T21:47:01Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Steve\_Saner](https://avatars.discourse-cdn.com/v4/letter/s/43a26b/32.png) [@Steve\_Saner](https://forum.ansible.com/u/Steve_Saner)\
**Post date:** [December 14, 2016, 9:55pm UTC](https://forum.ansible.com/t/service-module-with-slackware/23220/3 "2016-12-14T21:55:58Z")

</div>

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.

Steve

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [December 14, 2016, 9:58pm UTC](https://forum.ansible.com/t/service-module-with-slackware/23220/4 "2016-12-14T21:58:55Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Steve\_Saner](https://avatars.discourse-cdn.com/v4/letter/s/43a26b/32.png) [@Steve\_Saner](https://forum.ansible.com/u/Steve_Saner)\
**Post date:** [December 14, 2016, 10:04pm UTC](https://forum.ansible.com/t/service-module-with-slackware/23220/5 "2016-12-14T22:04:20Z")

</div>

Ah, okay, good to know. Then I will look into that. Thanks for the heads up.

Steve