Le 21/11/2016 à 23:54, Boris Rybalkin a écrit :
> Hello,
>
> I am porting uwsgi systemd config to snap and having some problem.
> Snap installs correctly while systemd cannot start the service (some
> other configuration issue). I think uwsgi will notify systemd that it
> has started and looks like snap daemon does not support Type=notify.
>
> Original config:
> ---------------------
> [Unit]
> Description=uWSGI Internal
> After=syslog.target
>
> [Service]
> ;User=platform
> ExecStart={{ app_dir }}/uwsgi/bin/uwsgi --ini {{ config_root
> }}/config/uwsgi/internal.ini
> Restart=always
> KillSignal=SIGQUIT
> Type=notify
> StandardError=syslog
> NotifyAccess=all
> Environment=LD_LIBRARY_PATH={{ app_dir }}/python/lib
>
> [Install]
> WantedBy=multi-user.target
> ---------------------
> Which is almost exact copy of the recommended config by uwsgi developers:
> http://uwsgi-docs.readthedocs.io/en/latest/Systemd.html
>
> This is snap version:
> ---------------------
> uwsgi:
> command: uwsgi/bin/uwsgi --ini ${SNAP_COMMON}/config/uwsgi/public.ini
> daemon: simple
> restart-condition: always
> plugs: [network, network-bind]
> ---------------------
>
> Snap way of defining systemd services seems very limited, is there a
> way to provide systemd version of the config in snapd?
Hey Boris,
This has been discussed some moons ago and indeed, it's not supported as
of today. Do you mind checking there is a bug for this in
https://launchpad.net/snappy and if none, file it?
Thanks!
Didier
--
Snapcraft mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
