RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 978954 - DOC: man page: no info what NAME means
Summary: DOC: man page: no info what NAME means
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: beta
: ---
Assignee: Václav Pavlín
QA Contact: Branislav Blaškovič
URL:
Whiteboard:
Depends On:
Blocks: 959971
TreeView+ depends on / blocked
 
Reported: 2013-06-27 11:21 UTC by Petr Sklenar
Modified: 2014-06-18 00:35 UTC (History)
6 users (show)

Fixed In Version: systemd-207-5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 09:44:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Sklenar 2013-06-27 11:21:27 UTC
Description of problem:
man page: no info what NAME means

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

How reproducible:
always

Steps to Reproduce:
1. systemctl [OPTIONS...] COMMAND [NAME...]
2. there is no explanation what NAME means

Actual results:
no explanation what NAME means

Expected results:
* what NAME means
* not obvious that you need '.service' in the comand
* not obvious that you need '=' in '--unit=NetworkManager.service', a space should work as well

Additional info:

Comment 3 Lukáš Nykrýn 2013-07-23 14:56:01 UTC
I think that this is sufficiently explained later in commands section, for example:

       start NAME...
           Start (activate) one or more units specified on the command line.

From above statement it is obvious that NAME corresponds to unit name.

Comment 4 Matthew Miller 2013-07-23 15:36:22 UTC
I think it would be helpful and not terribly burdensome to add a short explanation of usage to the top of the man page, in the DESCRIPTION section, which is currently very terse.

Comment 6 Branislav Blaškovič 2013-11-20 11:28:52 UTC
# man systemctl

I can see this in Description section (as mentioned in comment #4):

       For Unit Commands the NAME represents full name of unit.

           systemctl start foo.service

       For Unit File Commands the NAME represents full name of the unit file, or absolute path to the unit file.

           systemctl start /path/to/foo.service


Just one thing:
As far as I know: There should not be comma ',' before 'or' in english. :)

Comment 7 Branislav Blaškovič 2013-11-20 11:29:50 UTC
Additional information for comment #6:

It was tested with systemd-207-8.el7.x86_64.

Comment 8 Ludek Smid 2014-06-13 09:44:56 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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