Bug#783088: use $FOO instead of ${FOO} ?

[intrigeri]

Control: tag -1 + moreinfo

Hi,

Holger Levsen wrote (23 Apr 2015 09:45:30 GMT) :
 On Mittwoch, 22. April 2015, Rian Hunter wrote:
 So it was the configuration file's fault I
 guess, or maybe systemd. Where is this distinction for $FOO and ${FOO}
 in systemd documented? Bash doesn't make this distinction.

 I'm cloning this bug so that this get's fixed in the systemd documentation.

systemd.service(5) reads, in the section about ExecStart=:

   Basic environment variable substitution is supported.
   Use ${FOO} as part of a word, or as a word of its own, on
   the command line, in which case it will be replaced by the
   value of the environment variable including all whitespace
   it contains, resulting in a single argument. Use $FOO as
   a separate word on the command line, in which case it will
   be replaced by the value of the environment variable split
   at whitespace, resulting in zero or more arguments. To pass
   a literal dollar sign, use $$. Variables whose value is
   not known at expansion time are treated as empty strings.
   Note that the first argument (i.e. the program to execute)
   may not be a variable.

Isn't it enough?

Cheers,
--
intrigeri


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#783088: use $FOO instead of ${FOO} ?

[Holger Levsen]

clone 783088 -1
retitle -1 systemd should document distinction between $FOO and ${FOO}
reassign -1 systemd
tags -1 + upstream
thanks

Hi Rian,

On Mittwoch, 22. April 2015, Rian Hunter wrote:
  thanks for your bugreport. Can you confirm that using $FOO instead of
  ${FOO} fixes the issue?
 Yes, this fixes the issue. 

cool! thanks for reporting back! I'll try to get a fixed tlsdate into jessie 
8.1.

 So it was the configuration file's fault I
 guess, or maybe systemd. Where is this distinction for $FOO and ${FOO}
 in systemd documented? Bash doesn't make this distinction.

I'm cloning this bug so that this get's fixed in the systemd documentation.


cheers,
Holger




signature.asc
Description: This is a digitally signed message part.

Bug#783088: use $FOO instead of ${FOO} ?

[Holger Levsen]

control: reopen -1 
# I obviously ment to close the cloned bug...


signature.asc
Description: This is a digitally signed message part.

Bug#783088: use $FOO instead of ${FOO} ?

[Holger Levsen]

Hi Rian,

thanks for your bugreport. Can you confirm that using $FOO instead of ${FOO} 
fixes the issue?


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#783088: use $FOO instead of ${FOO} ?

[Rian Hunter]

On Wed, Apr 22, 2015 at 02:43:48PM +0200, Holger Levsen wrote:
 thanks for your bugreport. Can you confirm that using $FOO instead of ${FOO} 
 fixes the issue?

Yes, this fixes the issue. So it was the configuration file's fault I
guess, or maybe systemd. Where is this distinction for $FOO and ${FOO}
in systemd documented? Bash doesn't make this distinction.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org