We'll probably not support completely arbitrary passthrough options as it removes our ability to properly map the functionality into the confined world.
One instructive example is the commands that are already supported. They can't be just blindly executed as it might allow the snap to leave their confined space. That said, it already supports several options today, and it's easy to implement additional ones as required and sensible. On Wed, Feb 1, 2017 at 3:08 PM, Howard Cochran < [email protected]> wrote: > On Wed, Feb 1, 2017 at 11:09 AM, MikeB <[email protected]> wrote: > > I find myself having to write start scripts for daemon applications to > > (poorly) emulate the systemd service 'After' functionality for several > > of my snap applications. > > > > Is there any effort to add daemon ordering support to snapcraft/snapd? > > I think it would be generally useful. > > More generally, what is the correct way to specify any arbitrary systemd > directives that a daemon may need, such as User= for a service that > should run as non-root? Other common examples include > ConditionPathExists= EnvironmentFile= KillMode= ExecStartPre=, etc. > > Thanks, > Howard > > -- > Snapcraft mailing list > [email protected] > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/snapcraft > -- gustavo @ http://niemeyer.net
-- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
