Thanks for helping debug this! Similarly, using the extended profile name and executable path definition style:
profile test /tmp/test/{kill,sleep} { ...
works too, without need for aa-exec -p. With that work-around, I'm able to get my profile running happily again.
Thanks for helping debug this! Similarly, using the extended profile name and executable path definition style:
profile test /tmp/test/ {kill,sleep} {
...
works too, without need for aa-exec -p. With that work-around, I'm able to get my profile running happily again.