Red Hat Bugzilla – Bug 989236
systemd EnvironmentFile parser not support comment after command
Last modified: 2013-10-29 08:00:58 EDT
Description of problem:
lines in EnvironmentFile file with comment after assigning value (as
OPTIONS="string" # some comment
) are parsed badly. I know that 'man 5 systemd.exec' not specify this as alowed
syntax, but lots of old legacy /etc/systemd/ configuration files use this syntax, which is usual in shell. Though, for reasons of compatibility and better
file readability this should be perhaps legal syntax.
Version-Release number of selected component (if applicable):
Using this syntax, program started with this service unit exit with error message as "unknown option '-#'"
It was a concious design decision to disallow this. I'm pretty sure we don't want to change this.
@Harald, you disabled inline comments in http://cgit.freedesktop.org/systemd/systemd/commit/?id=98f59e5. Can you provide the justification and close this?
Hello Zbigniew, thank You for explication. But as I not understand what is mentioned by 'concious design' and how it relates with proclaimed
/etc/sysconfig/SomeShellOptions compatibility, I want to know Mr. Harald opinion.
(In reply to Zbigniew Jędrzejewski-Szmek from comment #1)
> It was a concious design decision to disallow this. I'm pretty sure we don't
> want to change this.
> @Harald, you disabled inline comments in
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=98f59e5. Can you
> provide the justification and close this?
explicit order of systemd master in command