What is wrong with my init.d script [Segmentation fault]

Question

I currently filter out data from a MQTT live stream. I then dump this datum into a csv file named mqtt.csv and the dumping process is done by executor_start_up_job.txt which is written in BASH.

I want to make the dumping of the filter daemon, i.e. in the background, and also want to make it in so that every time the system is rebooted it is done automatically. So I've concluded to write an init.d script, and contents of my code is:

#!/bin/bash
set -x

requested_command=$1

start() {

        /home/ed/start_up_job/executor_start_up_job.txt &
}
# Restart the Dump
stop() {

        killproc executor_start_up_job.txt
        echo
}
### main logic ###
case $requested_command in
  start)
        start
        ;;
  stop)
        stop
        ;;
  status)
        last_line=`cat mqtt.csv | tail -1`
        echo "last print line: $last_line"
        ;;
  restart)
        stop
        start
        ;;
  *)
        echo "Usage: $0 {start|stop|restart|status}"
        exit 1
        ;;
esac
exit 0

Once I have inserted set -x I get the following output:

+ ./MySQL_table_update_daemon.sh start
+ requested_command=start
+ start
+ exit 0

Q: It's my first time writing an init.d and I have written my code based on this example it doesn't work, as I get the error "segmentation fault"

Answer 1

No, it will not work because you have several syntax errors.

You also have some best practices violations.

Use bash -x on your file after correcting the errors to see it run. Read your script carefully and fix the syntax errors.

Some errors:

echo "last print line: `cat mqtt.csv | tail -1"
echo $"Usage: $0 {start|stop|restart|reload|status}"
# missing ;;

I stopped looking after 3. Note also it is normal to specify paths to executable files, usually with variables. It is also not normal to execute 'txt' files. You also aren't telling the user that you support 'condrestart' .