| 2015-09-02 22:17:48 |
Ricardo Kirkner |
description |
While writing a snappy package, I found an issue where systemd would not start the service defined in my snap package properly.
Upon closer inspection of the issue (thanks mvo!) we found that the problem was that the application itself was already forking to become a daamon, which requires the unit file to indicate this by adding Type=forking to the Service description.
After adding that stanza manually, the service started properly via systemd.
Please add support to snappy to either specify that the service handles forking itself, or by shipping a custom systemd unit file as part of the package. |
While writing a snappy package, I found an issue where systemd would not start the service defined in my snap package properly.
Upon closer inspection of the issue (thanks mvo!) we found that the problem was that the application itself was already forking to become a daamon, which requires the unit file to indicate this by adding Type=forking to the Service description.
After adding that stanza manually, the service started properly via systemd.
Please add support to snappy to specify that the service handles forking itself, thus causing the systemd unit file to have a Type=forking in the Service section. |
|
