I'm just trying to daemonize this simple python script:#!/usr/bin/python3print('hello')Here are my commands and the status:root@gw-0317STLG0067 /lib/systemd/system # systemctl enable test.serviceroot@gw-0317STLG0067 /lib/systemd/system # systemctl daemon-reloadroot@gw-0317STLG0067 /lib/systemd/system # systemctl start test.serviceroot@gw-0317STLG0067 /lib/systemd/system # systemctl status test.service* test.service - My Script Service   Loaded: loaded (/usr/lib/systemd/system/test.service; enabled; vendor preset:   Active: inactive (dead) since Sun 2016-07-31 10:06:29 UTC; 4s ago  Process: 20620 ExecStart=/root/test.py (code=exited, status=0/SUCCESS) Main PID: 20620 (code=exited, status=0/SUCCESS)Jul 31 10:06:29 gw-0317STLG0067 systemd[1]: Started My Script Service.Jul 31 10:06:29 gw-0317STLG0067 test.py[20620]: helloAnd here my service script:[Unit]Description=My Script ServiceAfter=multi-user.target[Service]Type=simpleExecStart = /root/test.py[Install]WantedBy=multi-user.targetWhy is it dead, and also what exactly should happen when you daemonize a print statement? Should it blow up the terminal?
systemd: Why is this service inactive (dead)?
systemd;python
It's dead because the script reaches its endpoint and terminates.  Why would a single print statement blow up the terminal.  A daemon usually runs in a loop that checks whether it's quitting time and terminates if so (or if it catches a signal from the kernel).