diff options
author | Lennart Poettering <lennart@poettering.net> | 2017-11-21 20:03:51 +0100 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2017-11-29 12:32:57 +0100 |
commit | b238be1e0d13f587d3a48645cea3f47d1dda3475 (patch) | |
tree | 5b37bd4715d555cbcc3d5875c445b5aecc1a1e49 /units | |
parent | core: process C-style escapes in UnsetEnvironment= (diff) | |
download | systemd-b238be1e0d13f587d3a48645cea3f47d1dda3475.tar.xz systemd-b238be1e0d13f587d3a48645cea3f47d1dda3475.zip |
core: enable specifier expansion for What=/Where=/Type=/SourcePath= too
Using specifiers in these settings isn't particularly useful by itself,
but it unifies behaviour a bit. It's kinda surprising that What= in
mount units resolves specifies, but Where= does not. Hence let's add
that too. Also, it's surprising Where=/What= in mount units behaves
differently than in automount and swap units, hence resolve specifiers
there too. Then, Type= in mount units is nowadays an arbitrary,
sometimes non-trivial string (think fuse!), hence let's also expand
specifiers there, to match the rest of the mount settings.
This has the benefit that when writing code that generates unit files,
less care has to be taken to check whether escaping of specifiers is
necessary or not: broadly everything that takes arbitrary user strings
now does specifier expansion, while enums/numerics/booleans do not.
Diffstat (limited to 'units')
0 files changed, 0 insertions, 0 deletions