I wonder if anyone can offer a simple solution to a problem which shows up when you have zm configured as a service that systmed can control and you then use zmpkg.pl to stop/start zm. The problem seems to be that if you use systemd's service control then the console and zmpkg.pl will tell you that the system is running or not according to what you ask systemctl to do.
However if you have zm running and then use the console or zmpkg.pl directly to stop zm systemd thinks it has failed (because the process that it started has died).
If you start zm using console/zmpkg.pl and then ask systemctl to start it, you get an error because it is already running.
I know that it could be argued that if you have zm installed as a service then you should only use systemd to restart it, but what if you make a change to an option and then you are told you need to restart - you'll almost certainly use the console.
I can think of a few possibilities of adding something to zmpkg.pl to pass requests on to systemctl when zm is installed as a service but that might get a little complicated as (at present) the service has to call zmpkg.pl.
Is there a way of letting systemd know that an external script has stopped/started something that it thinks it is controlling?