+++ This bug was initially created as a clone of Bug #656438 +++

Description of problem:

There is no references for YPSERV_ARGS and YPXFRD in /usr/share/doc/initscripts-8.45.30/sysconfig.txt used in /etc/sysconfig/network

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

rpm -qi initscripts
Name        : initscripts                  Relocations: (not relocatable)
Version     : 8.45.30                           Vendor: Red Hat, Inc.
Release     : 2.el5                         Build Date: Mon 13 Jul 2009 10:22:47 AM BRT
Install Date: Mon 22 Nov 2010 09:10:22 AM BRST      Build Host: ls20-bc2-14.build.redhat.com
Group       : System Environment/Base       Source RPM: initscripts-8.45.30-2.el5.src.rpm
Size        : 5471135                          License: GPLv2 and GPLv2+
Signature   : DSA/SHA1, Thu 30 Jul 2009 09:41:08 AM BRT, Key ID 5326810137017186
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL         : http://git.fedorahosted.org/git/initscripts.git
Summary     : The inittab file and the /etc/init.d scripts.
Description :
The initscripts package contains the basic system scripts used to boot
your Red Hat system, change runlevels, and shut the system down
cleanly.  Initscripts also contains the scripts that activate and
deactivate most network interfaces.


How reproducible:

Using commands.


Steps to Reproduce:

cat /usr/share/doc/initscripts-8.45.30/sysconfig.txt | grep YPSERV_ARGS
cat /usr/share/doc/initscripts-8.45.30/sysconfig.txt | grep YPXFRD

  
Actual results:

Nothins happends

Expected results:

We expected that returs this possible variables.

Additional info:

An working command returns:
cat /usr/share/doc/initscripts-8.45.30/sysconfig.txt | grep NISDOMAIN
NISDOMAIN=<nis domain name>

--- Additional comment from notting@redhat.com on 2010-11-23 20:53:50 EST ---

Those are not used by the initscripts package; NISDOMAIN is. While some service-specific parameters may be documented in sysconfig.txt due to legacy reasons, it is impossible for sysconfig.txt to realistically list all possible configuration values for all possible services that ship init scripts; service-specific configuration parameters need documented in the service itself.

--- Additional comment from ceolin@ulevel.com on 2010-11-24 08:14:32 EST ---

There is no documentation for YPSERV_ARGS and YPXFRD in package ypserv too.

How reproducible:

Using commands.


Steps to Reproduce:
cd /usr/share/doc/ypserv-2.19
grep -r YPSERV_ARGS .
grep -r YPXFRD .

Actual results:

Nothins happends

Expected results:

We expected that returs this possible variables.

Additional info:

--- Additional comment from ceolin@ulevel.com on 2010-11-24 08:24:06 EST ---

Complemeting:

How reproducible:

Using commands.

Steps to Reproduce:
man -K YPSERV_ARGS
man -K YPXFRD

Actual results:

Nothins happends

Expected results:

We expected that returs this possible variables.

--- Additional comment from ovasik@redhat.com on 2011-01-11 10:16:58 EST ---

YPSERV_ARGS is just envvar where you could provide arguments for ypserv (see man 8 ypserv).

YPXFRD is just envvar where you could provide arguments for rpc.ypxfrd (see man 8 rpc.ypxfrd).

Anyway, it would be better to document this either in the initscripts or in ypserv manpages. 

However, bugzilla is not a support tool, it is bug tracking tool. If you want to increase the priority of the ypserv update (and more info in these initscripts/manpages), please contact Red Hat product support - http://www.redhat.com/support/ .

--- Additional comment from varekova@redhat.com on 2011-04-21 09:28:09 EDT ---

Hello, please Jan what do you plan with this issue (man-pages fix/ documentation fix/ other option)?

--- Additional comment from hhorak@redhat.com on 2011-04-21 10:45:53 EDT ---

Created attachment 493878 [details]
patch of man pages

According to Bill's comment #1 I'd rather add these options to man pages. The attached patch extends man pages of ypserv, ypxfrd and yppasswdd.