Bug 72592 - [nis] NIS Domain Master fails as client of itself
Summary: [nis] NIS Domain Master fails as client of itself
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-12 18:50 UTC by Tony Shadwick
Modified: 2018-01-03 05:16 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tony Shadwick 2004-10-12 18:50:30 UTC
When setting up an NIS domain master per FreeBSD's documentation, you
are instructed to make a copy of master.passwd in /var/yp, remove any
system or administrative accounts and make domain-name, which succeeds.

This leaves you with your users' accounts in both /etc/master.passwd and
/var/yp/master.passwd, and if you wish to add a user, you must add to both
for the user to be valid on both the domain master and the nis domain.

The solution is to set the system up as an NIS client per FreeBSD's
documentation, by adding the following lines to /etc/rc.conf:

nisdomainname="domain-name"
rpcbind_enable="YES"
nis_client_enable="YES"
nis_client_flags="-S domain-name,server1,server2"

Remove the users from /etc/master.passwd that exist in /var/yp/master.passwd,
and add +::::::::: at the bottom of /etc/master.passwd.

However, after rebooting with this configuration, the users in
/var/yp/master.passwd do not register on the system.  

ypcat passwd
clnttcp_create failed
ypcat: no such map passwd.byname. reason: Can't communicate with portmapper

Connectivity to rpcbind is allowed through /etc/hosts.allow, and there are
no active firewall rules.

Fix: 

Unknown.
How-To-Repeat: Configure the system per FreeBSD's documentation as an NIS Server, then
add to that configuration the steps required to run as a client of itself.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2004-10-24 01:22:44 UTC
Responsible Changed
From-To: freebsd-i386->freebsd-bugs

This sounds more like a problem with the config files, or possibly 
even the documentation, than anything i386-specific.
Comment 2 Gavin Atkinson freebsd_committer freebsd_triage 2010-01-04 10:33:26 UTC
State Changed
From-To: open->feedback

To submitter: I suspect this was fixed several years ago, with the introduction 
of the new rc.d boot framework.  It appears that now at least, ypbind will 
always start after ypserv, so should be available on boot. 

Are you able to confirm that this is the case? 


Comment 3 Gavin Atkinson freebsd_committer freebsd_triage 2010-01-04 10:33:26 UTC
Responsible Changed
From-To: freebsd-bugs->gavin

Track
Comment 4 Gavin Atkinson freebsd_committer freebsd_triage 2010-01-04 10:37:31 UTC
State Changed
From-To: feedback->open

Mail to submitter bounces.  I'll try to test this myself at some point
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:03 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped