HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NIS ypbind question
Operating System - HP-UX
1834091
Members
1936
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2005 01:18 AM
09-05-2005 01:18 AM
Hello,
I set the slave server to bind with "-ypsetme" options. That means, that it should bind only to itself.
After I start nis client, I do:
ypwhich
And ofcourse I expect that it will bind to itself, but for some reason it's binds always to another slave and totaly ignores "-ypsetme" option.
I restarted it 20 times, nothing help.
Any ideas?
Thanx.
I set the slave server to bind with "-ypsetme" options. That means, that it should bind only to itself.
After I start nis client, I do:
ypwhich
And ofcourse I expect that it will bind to itself, but for some reason it's binds always to another slave and totaly ignores "-ypsetme" option.
I restarted it 20 times, nothing help.
Any ideas?
Thanx.
I don't give a damn for a man that can only spell a word one way. (M. Twain)
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2005 02:08 AM
09-05-2005 02:08 AM
Solution
Alex,
try to follow this procedure:
1)Log in as root to the slave server.
2)In the /etc/rc.config.d/namesvrs file, add -ypset to the YPBIND_OPTIONS variable as follows:
YPBIND_OPTIONS="-ypsetme"
3)Issue the following commands to restart ypbind (the NIS client process) on the slave server:
/sbin/init.d/nis.client stop
/sbin/init.d/nis.client start
4)Issue the following command to force the NIS client process on the slave server to bind to the server process on the same host:
/usr/sbin/ypset slave_server_name
5)Issue the following command to check whether the NIS slave server is working:
/usr/bin/ypwhich
The ypwhich command should return the host name of the slave server.
The ypsetme option allows you only to run ypset from the current host, but doesn't set itself the NIS server you want to connect to.
The server must specified with the ypset.
Regards,
Alex
try to follow this procedure:
1)Log in as root to the slave server.
2)In the /etc/rc.config.d/namesvrs file, add -ypset to the YPBIND_OPTIONS variable as follows:
YPBIND_OPTIONS="-ypsetme"
3)Issue the following commands to restart ypbind (the NIS client process) on the slave server:
/sbin/init.d/nis.client stop
/sbin/init.d/nis.client start
4)Issue the following command to force the NIS client process on the slave server to bind to the server process on the same host:
/usr/sbin/ypset slave_server_name
5)Issue the following command to check whether the NIS slave server is working:
/usr/bin/ypwhich
The ypwhich command should return the host name of the slave server.
The ypsetme option allows you only to run ypset from the current host, but doesn't set itself the NIS server you want to connect to.
The server must specified with the ypset.
Regards,
Alex
if you don't try, you'll never know if you are able to
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2005 04:05 AM
09-05-2005 04:05 AM
Re: NIS ypbind question
OK, thanx, I'll try it tomorrow.
Alex.
Alex.
I don't give a damn for a man that can only spell a word one way. (M. Twain)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2005 09:39 PM
09-05-2005 09:39 PM
Re: NIS ypbind question
Thanx, it seems that I didn't read the man explanation close enough.
Alex.
Alex.
I don't give a damn for a man that can only spell a word one way. (M. Twain)
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP