Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Path instances with dashes do not work #5072
Comments
added a commit
to bradbishop/systemd
that referenced
this issue
Jan 12, 2017
added a commit
to bradbishop/systemd
that referenced
this issue
Jan 12, 2017
added a commit
to bradbishop/systemd
that referenced
this issue
Feb 1, 2017
poettering
added
pid1
RFE
labels
Feb 1, 2017
|
yeah, we currently expect any unit listed in SYSTEMD_WANTS is properly escaped already, and if we notice it isn't we'll do minimal escaping, the same way "systemctl start …" will do it. But you really shouldn't rely on it, as it's not properly reversible, as you just noticed. A proper fix could be something like adding support for a new SYSTEMD_WANTS_INSTANCE property or so, where you'd specify a template name, and systemd would automatically fill in the device name in escaped form or so. |
poettering
referenced this issue
Feb 2, 2017
Open
basic: Use path escaping when mangling path instances #5073
pushed a commit
to openbmc/phosphor-led-sysfs
that referenced
this issue
Jun 12, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
bradbishop commentedJan 12, 2017
•
Edited 1 time
-
bradbishop
Jan 12, 2017
Submission type
systemd version the issue has been seen with
Used distribution
In case of bug report: Expected behaviour you didn't see
In case of bug report: Unexpected behaviour you saw
In case of bug report: Steps to reproduce the problem