Bug 11917 - authconfig doesn't allow specification of multiple NIS servers
Summary: authconfig doesn't allow specification of multiple NIS servers
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: authconfig
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-06-05 22:44 UTC by Michael S. Fischer
Modified: 2008-05-01 15:37 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2000-06-05 22:44:13 UTC


Attachments (Terms of Use)

Description Michael S. Fischer 2000-06-05 22:44:12 UTC
In its current incarnation, authconfig does not allow one to specify that
the server should explicitly bind to more than one server.  Only a single
server, or broadcast, is allowed.  This can cause problems like cron
sporadically spitting out error messages like

yp_all: clnt_call: RPC: Unable to receive; errno = Connection reset by peer

Which, according to Miquel van Smoorenburg at
<http://x59.deja.com/getdoc.xp?AN=606419756&CONTEXT=960243430.682622982&hitnum=3>,
is spit out to stderr by glibc during a NIS server switch.  In the article
referenced he mentions that explicitly setting the server names instead of
using broadcast should help reduce the problem.

However, I can't get authconfig to do it for me by having multiple
--nisserver command-line options.  I really would like this feature because
otherwise I'll have to tweak /etc/yp.conf manually during the
post-kickstart phase.

Comment 1 Nalin Dahyabhai 2000-06-10 21:05:31 UTC
This is now fixed in the version of authconfig in our build tree.  To simplify
the code that parses command-line options, you can list multiple NIS servers if
you separate them with commas (i.e., "--nisserver yp1.baz.com,yp2.baz.com").


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