Bug 698761 - systemctl status does not replace specifiers with their actual value
Summary: systemctl status does not replace specifiers with their actual value
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-21 17:37 UTC by Jóhann B. Guðmundsson
Modified: 2011-04-24 12:19 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-04-24 12:19:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.