Users trying to run a script as a daemon on a modern system should be using systemd:

[Unit]
Description=hit service
After=network-online.target

[Service]
ExecStart=/path/to/hit.sh

[Install]
WantedBy=multi-user.target

Save this as /etc/systemd/system/hit.service, and then you will be able to start/stop/enable/disable it with systemctl start hit, etc.

Old answer from 2015:

If you'd like to reuse your code sample, it could look something like:

#!/bin/bash

case "$1" in 
start)
   /path/to/hit.sh &
   echo $!>/var/run/hit.pid
   ;;
stop)
   kill `cat /var/run/hit.pid`
   rm /var/run/hit.pid
   ;;
restart)
   $0 stop
   $0 start
   ;;
status)
   if [ -e /var/run/hit.pid ]; then
      echo hit.sh is running, pid=`cat /var/run/hit.pid`
   else
      echo hit.sh is NOT running
      exit 1
   fi
   ;;
*)
   echo "Usage: $0 {start|stop|status|restart}"
esac

exit 0 

Naturally, the script you want to be executed as a service should go to e.g. /usr/local/bin/hit.sh, and the above code should go to /etc/init.d/hitservice.

For each runlevel which needs this service running, you will need to create a respective symlink. For example, a symlink named /etc/init.d/rc5.d/S99hitservice will start the service for runlevel 5. Of course, you can still start and stop it manually via service hitservice start/service hitservice stop

You need to write systemd service file.

Simplest script looks like this:

[Unit]
Description=Virtual Distributed Ethernet

[Service]
ExecStart=/usr/bin/YOUR_SCRIPT

[Install]
WantedBy=multi-user.target

Also you need: systemctl daemon-reload after creating new service.

The problem is that, when the script runs as a service, it does not run as "you": it does not have your environment. Specifically, it does not have your PATH variable.

Either add /home/<usernamehere>/.opam/default/bin to the PATH in your script, or simply hardcode the full path for that program.

Your shellscript.service definition is working. The shell script was executed, but some command on line #25 of the script returned an error message:

AthanMayT.txt: No such file or directory

This caused the script to exit with status code 1, indicating a failure.

Errors like this are often caused by the current working directory not being what you expected.

You should note that any process or script executed by systemd is not normally executed in any user's home directory: the default working directory for any process started by systemd will be the system's root directory, or /.

To troubleshoot, run your script like this to simulate the conditions when executed by systemd:

cd /
/usr/bin/script.sh

You should probably use full pathnames for every file you reference in your script, or explicitly include a cd /full/path/to/some/directory in the beginning of the script to ensure that relative path names are interpreted the way you expect.

Use su to run the script as a different user:

daemon su -c /home/webreports/report-listen johndoe

where johndoe is the user you want it to run as.

Put the script in /etc/init.d/myservice, then symlink it to /etc/rc.d/S99myservice.

Your .service file should look like this:

[Unit]
Description=Spark service

[Service]
ExecStart=/path/to/spark/sbin/start-all.sh

[Install]
WantedBy=multi-user.target

Now, take a few more steps to enable and use the .service file:

1. Place it in /etc/systemd/system folder with a name like myfirst.service.

2. Make sure that your script is executable with:

    chmod u+x /path/to/spark/sbin/start-all.sh
   

3. Start it:

    sudo systemctl start myfirst
   

4. Enable it to run at boot:

    sudo systemctl enable myfirst
   

5. Stop it:

    sudo systemctl stop myfirst
   

Notes

1. You don't need to launch Spark with sudo in your service, as the default service user is already root.

2. Look at the links below for more systemd options.

Moreover

Now what we have above is just rudimentary, here is a complete setup for spark:

[Unit]
Description=Apache Spark Master and Slave Servers
After=network.target
After=systemd-user-sessions.service
After=network-online.target
 
[Service]
User=spark
Type=forking
ExecStart=/opt/spark-1.6.1-bin-hadoop2.6/sbin/start-all.sh
ExecStop=/opt/spark-1.6.1-bin-hadoop2.6/sbin/stop-all.sh
TimeoutSec=30
Restart=on-failure
RestartSec=30
StartLimitInterval=350
StartLimitBurst=10
 
[Install]
WantedBy=multi-user.target

To setup the service:

sudo systemctl start spark.service
sudo systemctl stop spark.service
sudo systemctl enable spark.service

Further reading

Please read through the following links. Spark is a complex setup, so you should understand how it integrates with Ubuntu's init service.

• https://datasciencenovice.wordpress.com/2016/11/30/spark-stand-alone-cluster-as-a-systemd-service-ubuntu-16-04centos-7/
• https://www.digitalocean.com/community/tutorials/understanding-systemd-units-and-unit-files
• https://www.freedesktop.org/software/systemd/man/systemd.unit.html