Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - HP-UX
- >
- System Administration
- >
- NIS netgroup not propogating on slave server
System Administration
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-23-2009 11:35 AM
11-23-2009 11:35 AM
NIS netgroup not propogating on slave server
Hi there --
We recently merged two NIS domains into one. The NIS master and slave servers of second domain were made into slaves to the master in the first domain.
I noticed that a change made to the netgroup file on the master did not appear in its counterpart on either of the slave servers. A check of the time stamps on the slave servers indicated the netgroup file on each was not updated from the master.
When the merge took place, the ypmake command was run on the master server, and the ypinit command was run on the slave servers. The domain user accounts were able to log into all servers without issue.
Is there an additional step(s) or command(s) that need to be run in order to synchronize all files between the slaves and the master? Thanks.
We recently merged two NIS domains into one. The NIS master and slave servers of second domain were made into slaves to the master in the first domain.
I noticed that a change made to the netgroup file on the master did not appear in its counterpart on either of the slave servers. A check of the time stamps on the slave servers indicated the netgroup file on each was not updated from the master.
When the merge took place, the ypmake command was run on the master server, and the ypinit command was run on the slave servers. The domain user accounts were able to log into all servers without issue.
Is there an additional step(s) or command(s) that need to be run in order to synchronize all files between the slaves and the master? Thanks.
A Journey In The Quest Of Knowledge
1 REPLY
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-23-2009 11:47 AM
11-23-2009 11:47 AM
Re: NIS netgroup not propogating on slave server
You need to manually update the ypservers map on the new NIS master and put in there the names of the new slave servers (the master and slave servers of the second domain).
The file is in /var/yp/domainname/ypservers.pag
1. Extract the contents of the map file into a text file
makedbm -u ypservers > ypservers.txt
2. Edit the ypservers.txt file and add the new slave servers
3. Create the new map files from the edited text file
makedbm ypservers.txt ypservers
4. Verify the contents of the new map file with "strings ypservers.pag"
5. Push the remaining maps as needed. You may have to force a push by touching each source file.
The file is in /var/yp/domainname/ypservers.pag
1. Extract the contents of the map file into a text file
makedbm -u ypservers > ypservers.txt
2. Edit the ypservers.txt file and add the new slave servers
3. Create the new map files from the edited text file
makedbm ypservers.txt ypservers
4. Verify the contents of the new map file with "strings ypservers.pag"
5. Push the remaining maps as needed. You may have to force a push by touching each source file.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP