# view logs (each line is short)
journalctl
# view logs with normal line lengths (lines are not contracted), get used to always running -a (For all), a for "showing All of the line".
journalctl -a
# show the 100 latest lines of logs
journalctl -an100
# following the log (synonymous with "tail -f /var/log/syslog"), f for "Following"
journalctl -fa

[Unit]
Description=My Simple Service
[Service]
Type=forking
# The PID file is optional, but recommended in the manpage
# "so that systemd can identify the main process of the daemon"
PIDFile=/var/run/myservice.pid
ExecStart=/usr/bin/myservice --daemon --pidfile /var/run/myservice.pid
[Install]
WantedBy=multi-user.target

^ The difference is in the way the dependencies are handled. If some other services depend on myservice.service,
then, in the first example, systemd will be able to run them as soon as it starts myservice.
In the second example, systemd will wait until myservice forks. The difference matters,
because myservice creates its control socket after starting, but before forking.
So, in the first example, there is some chance that systemd will start something that
tries to connect to the socket before myservice creates it.