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.

Description of problem:
Please expand the systemd manpage in relation to the `--test` flag. We need to explicitly say that it can only be run in maintenance mode and/or that it's not something you typically run. Right now it can be interpreted as you'll get a list of the startup sequence, which is really not possible since systemd uses socket activation and you can't get everything (socket activation is dynamic and not deterministic). 


Version-Release number of selected component (if applicable):
systemd-208-20.el7_1.5

How reproducible:
Always 

Steps to Reproduce:
1. man systemd
2. search for "--test"

Actual results:
The "--test" option is unclear.

Expected results:
We need to explicitly say that it can only be run in maintenance mode and/or that it's not something you typically run.

I think that from the current description it is clear:

Determine startup sequence, dump it and exit. This is an option useful for debugging only.

Thanks, Lukáš. I think part of the issue was the --test functionality was broken in RHEL 7.1.  Since this is working as expected in RHEL 7.2 I can understand this being closed.