pkill | Provides Golang wih an easy to use and cross-platform method

Create a file like /etc/init.d/test

Ok. What I was thinking is something like this.

I think you should have to use systemd for this case: https://github.com/torfsen/python-systemd-tutorial

After some research, I came to know that all these kill commands are just killing the process whereas in this case, we need to stop the process.

This thing I have achieved by

The short answer is to redirect the standard file descriptors (standard input, output, and error) for the script's java command like this:

"$@" is an array of the arguments passed to your script, "$*" is a string of all of those arguments concatenated with blanks in between.

"${*:--}" is the string of arguments if any were provided (:-), or - otherwise which means "take input from stdin" otherwise.

"${@:--}" is the array of arguments if any were provided (:-), or - otherwise which means "take input from stdin" otherwise.

Well, if the dummy folders did get created, that means the sudo statements work, so i'd say theres a 99%+ chance that python was infact started.

I'm guessing the problem is that you havent specified the path for the python file, and your working directory likely isn't what you're expecting it to be.

change:

I'm trying to figure out something similar to you, but not quite the same..

This solution got my script python script running upon internet connection, I can check the logs and everything is working fine:

Raspbian - Running A Script After An Internet Connection Is Established

However, my script uses notify-send to send notifications to my window manager which I can't seem to get working with systemd - the script works when run inside of the user space so I assume it's something to do with systemd and Xorg. Hopefully that shouldn't be a problem for you, I hope this solves your issue.

You shouldn't need a bash script in the middle, I got systemd service to run my python script with chmod u+x .py and putting #!/usr/bin/env python3 at the top of the python file so that it's executable directly under the .service file like so:

ExecStart=/path/to/file/file.py

As @Aserre mentioned in the comments, you'll need to use double quotes instead of single quotes in your pkill command so that the value of the shell variables is replaced in the string.

Also, take into account that pkill sends SIGTERM by default. Therefore, test.py should have a signal handler to shutdown when it receives SIGTERM. If test.py doesn't have a signal handler, it will ignore the signal and continue to live. If that is the case, use pkill -9, which will kill ptest.py since signal 9 can't be ignored: