![]() I will see Security Policy exceptions like: Log: apparmor="ALLOWED" operation="exec" profile="snap.snap_name.my-service" name="/usr/bin/snap" pid=24603 comm="sh" requested_mask="x" denied_mask="x" fsuid=0 ouid=0 target="snap.snap_name.my-service-service//null-/usr/bin/snap" I have tried running something like: sprintf(command, "snap connect %s:mount-observe :mount-observe", SNAP_NAME) įrom c code and I have also tried running: snap connect :mount-observe :mount-observeĬommand: bin/my-wrapper-that-will-call-my-app.shīut neither seems to provide the desired result. I'm very eager to find a way to connect these 'non-auto' plugs through some other mechanism. However, our application runs as a service - the command line will not be available to manually connect this interface, and access to this, and other plugs, is mandatory for the normal function of our application. I am familiar with how to connect snaps from the command line: snap connect :mount-observe :mount-observe ![]() My question is in regards to connecting non-auto-connect snap interfaces, more specifically, how to do it from either code (c) or at service start via systemd. Please note that the raspberry pi is not our final target platform but it makes a suitable POC for the time being. Linux localhost.localdomain 4.4.0-1030-raspi2 #37-Ubuntu SMP Thu Oct 20 15:06: armv7l armv7l armv7l snap -version I'm currently leading an effort to make our application available as a snap for Ubuntu Core 16.04 LTS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |