Originally Posted by rouvas
Your deployment (of what?) depends on starting services on machines?
What are you deploying?
It seems pointless to me.
By deploying I meant, compile code, pack a jar or a binary rsync with the server machine added the new service script and restart the service.
I have scripts that do all of this.
Until now the server machines were always Debian or Ubuntu distros, so my scripts have a line similar to service "service" start.
Since I want portability I am emulating this command.
Apart for portability there is another issue: Slackware is not that widely used (as sad as it is)
So I can not rewrite my deploy scripts because there are other persons involved that do not have contact with Slackware.
In summary portability and a common interface for my lab.
Correct me if I'm wrong but isn't the service command a RedHat derivative?
Any way you'll be happy to know that Slackware has the ability to start and stop scripts that use the sysvinit style used by other distros, you'll just need to write a script that sets them up in the right directories and they will run automatically.
See /etc/rc.d and its sub-directories.
Maybe service command is from RedHat.
I can only say it is available in Debian.
The issue is not running the script, the issue is to have a deploy script that deploys in Slackware and (at least) Debian distros.
I am not saying it is useful for everyone.
If you like the idea use it, if you have fixes to the script please tell me.
If you do not need this emulation do not use it.
We have a choice now