Figured it out - here’s the equivalent systemd script:

[Unit]
Description=simple python script

[Service]
Environment= MY_ENVIRONMENT_VAR =/path/to/file.config
WorkingDirectory=/path/to/script
ExecStart=/usr/bin/python script.py
Restart=always

[Install]
WantedBy=multi-user.target

This file was in my app directory, so I created a dynamic link to it in the systemd directory:

/etc/systemd/system/

by doing:

ln -s /path/to/file/my_systemd_script.service /etc/systemd/system/my_systemd_script.service

If you get a “Too many levels of symbolic links” error: See @nabito answer below, just copy the file into the /etc/systemd/system/ folder with a cp instead of creating a symbolic link.

Then I can start it with:

systemctl daemon-reload
systemctl enable my_systemd_script.service
systemctl start my_systemd_script.service

Thanks for the tip, however I followed your steps and got an error due to symlink the .service when trying to ‘systemctl enable mysystemdscript.service’

Failed to execute operation: Too many levels of symbolic links.

This is in Ubuntu 16.04.1 LTS upgraded from 14.04. The solution I took is to put the actual .service in /etc/systemd/system. Seems systemctl will try to create another symlink for it, as seen in the success output from 'systemctl enable’ command.

Created symlink from /etc/systemd/system/multi-user.target.wants/mysystemd.service to /etc/systemd/system/mysystemd.service.

Thanks, for this conversation i have same problem and i have resolved it but i also want to have a log file for that python script so is there any way to add log file??