I downloaded a python script allowing me to perform certain tasks. It requires a start/stop parameter to start or stop the service respectively. Unfortunately I have to run multiple instances of this script, which daemonizes itself after being launched. I created a service file that allows me to pass in a variable to start/stop the multiple instances individually. Everything looks like it works, but the script really is never run (as checked via ps aux and manual testing). I am sure it is probably a misconfiguration on my part. Wondering your thoughts? How would you do this differently?

File: /etc/systemd/system/watcher@.service
Content:
Code:
[Unit]
Description=watcher daemon for /nonprodnfs/%I
After=network.target

[Service]
Environment=START=start
Environment=STOP=stop
Type=forking
Restart=on-failure
RestartSec=1
User=root
ExecStart=/usr/bin/python "/home/john/scripts/watcher/%i/watcher.py" ${START}
ExecStop=/usr/bin/python "/home/john/scripts/watcher/%i/watcher.py" ${STOP}

[Install]
WantedBy=multi-user.target
For instance, I attempt to start with:
Code:
systemctl start watcher@directoryname
It doesn't error out, but when I run a systemctl status it shows the following:
Code:
● watcher@directoryname.service - watcher daemon for /nonprodnfs/directoryname
   Loaded: loaded (/etc/systemd/system/watcher@.service; disabled; vendor preset: disabled)
   Active: inactive (dead)