Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Also "mask" services when disabling them #61
+10
−1
Conversation
ogra1
merged commit 4c778be
into
snapcore:master
Oct 12, 2017
1 check passed
continuous-integration/travis-ci/pr
The Travis CI build passed
Details
added a commit
to mvo5/snappy
that referenced
this pull request
Nov 30, 2017
added a commit
to mvo5/snappy
that referenced
this pull request
Nov 30, 2017
mvo5
referenced this pull request
in snapcore/snapd
Nov 30, 2017
Merged
systemd: add support for the mask/unmask operations #4331
added a commit
to mvo5/snappy
that referenced
this pull request
Nov 30, 2017
mvo5
referenced this pull request
in snapcore/snapd
Nov 30, 2017
Merged
corecfg: also "mask" services when disabling them #4332
added a commit
to snapcore/snapd
that referenced
this pull request
Dec 1, 2017
added a commit
to snapcore/snapd
that referenced
this pull request
Dec 1, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mvo5 commentedOct 12, 2017
In addition to disabling services when
snap set service.{ssh,syslog}.disable=trueis called we need tomask them. The reason is that the /etc/systemd/system directory
is marked "synced" and the core snap has a "syslog.service" symlink.
So on each boot if there is no "syslog.service" (or ssh) link there
writable-path will happily copy it. This is not what we want. By
using "mask" in addition to disable systemd will create a symlink
with the name of the service to /dev/null. This prevents
writable-path from interfering.