improve systemd configuration support
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
Fix Released
|
Wishlist
|
Sergio Schvezov | ||
snapd |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
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/
Restart=always
KillSignal=SIGQUIT
Type=notify
StandardError=
NotifyAccess=all
Environment=
[Install]
WantedBy=
-------
Which is almost exact copy of the recommended config by uwsgi developers:
http://
This is snap version:
-------
uwsgi:
command: uwsgi/bin/uwsgi --ini ${SNAP_
daemon: simple
restart-
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?
Changed in snapcraft: | |
status: | In Progress → Fix Committed |
Changed in snapcraft: | |
status: | Fix Committed → Fix Released |
affects: | snappy → snapd |
Branch here: https:/ /github. com/snapcore/ snapd/pull/ 2363