{"id":7346,"date":"2018-11-26T19:49:36","date_gmt":"2018-11-26T16:49:36","guid":{"rendered":"https:\/\/www.howtoforge.com\/linux-service-command\/"},"modified":"2018-11-26T19:49:36","modified_gmt":"2018-11-26T16:49:36","slug":"linux-service-command-tutorial-for-beginners-with-examples","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/linux-service-command-tutorial-for-beginners-with-examples\/","title":{"rendered":"Linux service Command Tutorial for Beginners (with Examples)"},"content":{"rendered":"
\n

The service command lets you run a System V init script. In this tutorial, we will briefly discuss this tool using some easy to understand examples. But before we do that, it’s worth mentioning that all examples here have been tested on an Ubuntu 18.04 LTS machine.<\/p>\n

Linux service command<\/h2>\n

Here are the available syntax for the service command in Linux:<\/p>\n

service SCRIPT COMMAND [OPTIONS]
service --status-all<\/p>
service --help | -h | --version<\/p><\/code><\/pre>\n
And here’s how the man page explains it:<\/p>\n
service\u00a0 runs\u00a0 a System V init script or systemd unit in as predictable an environment as possible,removing most environment variables and with the current working directory set to \/.
The SCRIPT parameter specifies a System V init script, located in \/etc\/init.d\/SCRIPT, or the name of a systemd unit. The\u00a0 existence of\u00a0 a\u00a0 systemd unit of the same name as a script in \/etc\/init.d will cause the unit to take precedence over the init.d script. The supported values of COMMAND depend on the invoked script. service passes COMMAND\u00a0 and OPTIONS to the init\u00a0 script\u00a0 unmodified.For systemd units, start, stop, status, and reload are passed through to their systemctl\/initctl equivalents.<\/p>
All\u00a0 scripts\u00a0 should\u00a0 support at least the start and stop commands.\u00a0 As a special case, if COMMAND is --full-restart, the script is run twice, first with the stop command, then with the start command.<\/p>
service --status-all runs all init scripts, in alphabetical order, with the status command. The status is [ + ]\u00a0 for\u00a0 running\u00a0 services,\u00a0 [\u00a0 -\u00a0 ]\u00a0 for\u00a0 stopped services and [ ? ] for services without a status command.\u00a0 This option only calls status for sysvinit jobs.<\/p><\/code><\/pre>\n
How to use service command?<\/h2>\n
The usage of the ‘service’ command line tool isn’t complicated at all. Let’s talk about how you can use this utility when it comes to handling scripts like httpd and sshd.<\/p>\n
Here’s how you run a script using service:<\/p>\n
service httpd start<\/code><\/pre>\n
Here’s how you stop an already running script using service:<\/p>\n
service sshd stop<\/code><\/pre>\n
Here’s how you fetch status for a script:<\/p>\n
service httpd status<\/code><\/pre>\n
Here’s how you restart and already-running service:<\/p>\n
service sshd restart<\/code><\/pre>\n
Conclusion<\/h2>\n
Depending on your\u00a0privileges<\/span> as Linux user, you may want to run all the above examples using the ‘sudo’ command. To learn more about the ‘service’ command, head to its man page<\/a>.<\/p>\n<\/article>\n