This blind assumption that all units starting with snap[-.] are ours to
do with as we see fit seems suspect. snapd does not own the snap prefix
exclusively. We could imagine a package with a snap-shotting-
service.service which would now get randomly stopped when snapd is
removed:
+ mounts="$(systemctl list-unit-files | grep '^snap[-.].*\.mount' | cut -f1
-d ' ')"
+ services="$(systemctl list-unit-files | grep '^snap[-.].*\.service' | cut
-f1 -d ' ')"
As we are making these dynamically can we not record them or tag them
internally so we are sure they are ours? Or perhaps make them symlinks
to somewhere else so we can positively identify the ones which we made.
** Changed in: snapd (Ubuntu Xenial)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605303
Title:
[SRU] 2.11
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1605303/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
