Bug 698761

Summary:	systemctl status does not replace specifiers with their actual value
Product:	[Fedora] Fedora	Reporter:	Jóhann B. Guðmundsson <johannbg>
Component:	systemd	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	johannbg, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-04-24 12:19:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jóhann B. Guðmundsson 2011-04-21 17:37:46 UTC

Description of problem:

When running systemctl status foo the ouput does not replace the specier with it's value. For example ExecStart with %i in the paths 

Version-Release number of selected component (if applicable):

systemd-24-1.fc15.x86_64

How reproducible:
 

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Lennart Poettering 2011-04-24 12:19:32 UTC

This is actually a feature. Wildcards are only replaced at time of execution, not at reload, and we want to make that clear. That means if you use "systemctl set-environment" or edit a file specified in EnvironmentFile the changes will apply on next start of your service, not only when you reload systemd. 

If we would do wildcard expansion also on "systemctl" the output could get very confusing, since what is executed is not necessarily what we show.

So I think we shouldn't try to do this.