When creating a snap, and according to the syntax of the snapcraft.yaml file, the daemon
keyword can be added to specify that the app will be run as a system service. As an example of such declaration:
apps:
tinyproxy:
command: ./launcher.sh
daemon: simple
plugs: [network,network-bind]
However, what does it exactly mean to be a system service in a snap? That is, what's their lifecycle (start, restart, stop...)? Can I monitor them running in the system with the usual tools (ps
, top
, etc)?