[systemd-bugs] [Bug 82832] New: Services with special characters in the name which fail during "systemctl start" display an incorrect error message
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Aug 19 18:47:59 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=82832
Priority: medium
Bug ID: 82832
Assignee: systemd-bugs at lists.freedesktop.org
Summary: Services with special characters in the name which
fail during "systemctl start" display an incorrect
error message
QA Contact: systemd-bugs at lists.freedesktop.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: seejay.11 at gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: general
Product: systemd
Created attachment 104929
--> https://bugs.freedesktop.org/attachment.cgi?id=104929&action=edit
Terminal session providing a better view of the issue
Running a command like the following will give a bad error message on failure:
systemctl start 'netctl at wlo1\x2dSKY8B120.service'
The error message given is:
Job for netctl at wlo1\x2dSKY8B120.service failed. See 'systemctl status
netctl at wlo1\x2dSKY8B120.service' and 'journalctl -xn' for details.
Typing "systemctl status netctl at wlo1\x2dSKY8B120.service" into the shell does
not have the expected behaviour as the backslash is parsed by the shell which
causes systemctl to check the wrong service. The service name should be quoted
or adequately escaped.
The attached log shows "netctl" being used, because I originally assumed this
was a netctl bug. I have tried this with "systemctl start
'netctl at wlo1\x2dSKY8B120.service'" and it prints the same message with the same
mistake.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140820/c5b48d10/attachment.html>
More information about the systemd-bugs
mailing list