Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira ( 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 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 "", 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 1181591 - No Documentation= line in the sshd.service file
Summary: No Documentation= line in the sshd.service file
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openssh
Version: 7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Jakub Jelen
QA Contact: Stanislav Zidek
Depends On:
Blocks: 1181593 1191021
TreeView+ depends on / blocked
Reported: 2015-01-13 12:34 UTC by Karsten Weiss
Modified: 2016-02-09 08:29 UTC (History)
3 users (show)

Fixed In Version: openssh-6.6.1p1-13.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1181593 (view as bug list)
Last Closed: 2015-11-19 08:02:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2088 0 normal SHIPPED_LIVE Moderate: openssh security, bug fix, and enhancement update 2015-11-19 08:38:51 UTC

Description Karsten Weiss 2015-01-13 12:34:50 UTC
Description of problem:

There is no "Documentation=" line in "[Unit]" section of the
/usr/lib/systemd/service/sshd.service that references sshd's man pages.

That's why "systemctl status sshd.service" doesn't show the "Docs:"
section and "systemctl help sshd.service" doesn't open the man pages.

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


How reproducible:

Query the sshd.service.

Steps to Reproduce:
1. systemctl status sshd.service
2. systemctl help sshd.service

Actual results:

"systemctl status sshd.service" doesn't show a "Docs:" section

"systemctl help sshd.service" prints "Documentation for sshd.service not known." 

Expected results:

"systemctl status sshd.service" should show a "Docs:" section:
# systemctl status sshd.service
sshd.service - OpenSSH server daemon
   Loaded: loaded (/etc/systemd/system/sshd.service; enabled)
   Active: active (running) since Mon 2015-01-12 13:58:24 CET; 23h ago
     Docs: man:sshd(8)

"systemctl help sshd.service" should open the man pages.

Additional info:

The Documentation= line in sshd.service could look like this:

# cat sshd.service
Description=OpenSSH server daemon
Documentation=man:sshd(8) man:sshd_config(5)

The same applies to /usr/lib/systemd/service/sshd.socket.

Also, there are some other systemd unit files without a "Documentation=" line.
You should probably add a generic test for that.

Comment 6 errata-xmlrpc 2015-11-19 08:02:35 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

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