Bug 1374436

Summary:	manpage for rpc.rstatd incorrectly states that it is used with rpc.lockd during crash recovery
Product:	Red Hat Enterprise Linux 7	Reporter:	Frank Sorenson <fsorenso>
Component:	rusers	Assignee:	Petr Kubat <pkubat>
Status:	CLOSED ERRATA	QA Contact:	Vaclav Danek <vdanek>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	hhorak, jscotka, pkubat, sauchter, vdanek
Target Milestone:	rc	Keywords:	FastFix, ManPageChange, Patch
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 12:20:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1298243, 1393868

Description Frank Sorenson 2016-09-08 16:18:51 UTC

Description of problem:

The manpage for rpc.rstatd states:
	They are also used by the rpc.lockd(8) server during crash recovery.

(referring to recovery of file locks over nfs during crash recovery)


It is 'rpc.statd' which deals with nfs file locks, not 'rpc.rstatd'


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

RHEL 7.2 - rusers-server-0.17-79.el7.x86_64


How reproducible:

	It's documentation...  

Steps to Reproduce:

	1. man rpc.rstatd

The sentence stating "They are also used by the rpc.lockd(8) server during crash recovery." and the SEE ALSO referencing 'rpc.lockd(8)' should be removed from the manpage:

/usr/share/man/man8/rpc.rstatd.8.gz

Comment 8 Vaclav Danek 2017-02-02 13:45:06 UTC

Package:
rusers-0.17-80.el7.x86_64
rusers-server-0.17-80.el7.x86_64

Sentence and SEE ALSO reference removed.
=> Verified

Comment 10 errata-xmlrpc 2017-08-01 12:20:19 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.

https://access.redhat.com/errata/RHBA-2017:1907