You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…te COMMENT_ESCAPE
When we see a "\" in COMMENT state, we change the state to COMMENT_ESCAPE. When we got
a new character, we reset the state to COMMENT, but this character is not dispatched.
Usually the character is NEWLINE, if so we will stay in COMMENT state until we find
the next NEWLINE.
fix: systemd/systemd#27975
…te COMMENT_ESCAPE
When we see a "\" in COMMENT state, we change the state to COMMENT_ESCAPE. When we got
a new character, we reset the state to COMMENT, but this character is not dispatched.
Usually the character is NEWLINE, if so we will stay in COMMENT state until we find
the next NEWLINE.
fix: systemd/systemd#27975
systemd version the issue has been seen with
253
Used distribution
Fedora CoreOS 38
Linux kernel version used
6.2.15-300.fc38.x86_64
CPU architectures issue was seen on
x86_64
Component
systemd
Expected behaviour you didn't see
I have a unit that references an
EnvironmentFile
. My environment file looks like this:My expectation is that FOO will be set to bar, as the line-continuation character should be ignored since it is part of a comment.
For reference: POSIX shells (tried with sh and bash) ignore the line-continuation character at the end of a comment. For example:
will print
bar
.Unexpected behaviour you saw
systemd is parsing the line continuation character at the end of the comment line, and thus including the next
FOO=bar
line as part of the comment.Steps to reproduce the problem
No response
Additional program output to the terminal or log subsystem illustrating the issue
No response
The text was updated successfully, but these errors were encountered: