Snap issue with python daemon

[MikeB]

As a follow-up, using the python-systemd package to change the daemon
to 'notify' works in snappy - the snap is installed and the daemon is
running as expected.

http://gist.github.com/mabnhdev/17a8cb7bdc4df947a1c24d42c32b1daf

Mike

On Thu, Apr 6, 2017 at 12:26 PM, MikeB <mabnhdev at gmail.com> wrote:
> I'm using the python-package to daemonize a python command.
>
> In my snapcraft, I list my command as a forking daemon.
>
> When I run the command directly from command line, it does exactly
> what I expect, it damonizes and runs forever while the parent exits.
>
> When I try to install the snap, the installation hangs starting the
> snap until it finally times out.
>
> I see my command running during the start up - I see it logging to
> syslog as expected. Interestingly, it leaves the command running after
> the timeout.  I have to manually kill it.
>
> A simple example of the snapcraft.yaml and the test-daemon can be
> found at https://gist.github.com/mabnhdev/121154d3c6fd830d60a60eaee3c33c7b
>
> It seems as if the default behavior of the python-daemon package is
> not sufficient for snappy.  What else needs to happen?
>
> Regards, Mike