How to add the old run "service" to kali sana or rolling

[pedropt]

For those that came from kali wheezy and miss the command:
ex : "service network-manager start" that changed in kali jessie to "/etc/init.d/network-manager start"
all you have to do to add this old command to your kali is create a script in your "/usr/bin" with the name :

service

and add this bash code to it :

#!/bin/bash
cmd=$1
run=$2
/etc/init.d/$cmd $run
exit

then add execution permissions to this script by typing :

chmod +x /usr/bin/service

and its done .

Now you can stop , restart or run your linux services like it was before by typing :

service nginx start

or any other service in /etc/init.d/ directory .

Last none :
On a migration from wheezy to jessie (moto ->jessie) kali , you will have a filename with the name "service" on your "/usr/sbin" folder that will be not used anymore .

rename that file , so the terminal console does not give priority to it instead the new file .

mv /usr/sbin/service /usr/sbin/service.bak

then close your terminal and open it again and it should work perfectly

[steev]

Instead of creating this random file....

Either do it as an alias in your ~/.bashrc ; or (ideally) learn the new way which is using systemctl (which is good because init scripts are going away slowly).

so instead of service servicename start you do systemctl start servicename

[pedropt]

For that you just need to change the script to :

#!/bin/bash
cmd=$1
run=$2
systemctl $cmd $run
exit

and instead using "service network-manager start" , you must use "service start network-manager" , but that defies the main objective of this script originally and it makes no sense using "service" instead "systemctl".

I did this script particularly for those that came from wheezy to jessie , and not for those that the first time they saw kali was on 2.0 version , because those are already use to "systemctl" command .

[mmusket33]

The service command for network-manager in kali-linux R2 accepts:

service NetworkManager start as well as service network-manager start

We are unsure if kali-linux sana accepts service network-manager start

MTeams only noticed this during a program audit of airmon-ng especially the airmon-ng check kill comand.

As a side note we still think that if you evoke airmon-ng check kill and then try and restore network-manager later with service NetworkManager start then some parts of network-manager do not function. This is because airmon-ng check kill also evokes service avahi-daemon stop. See line 997 in /usr/sbin/airmon-ng


Musket Teams