HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NIS problem..
Operating System - HP-UX
1833325
Members
3006
Online
110051
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
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
08-24-2006 04:58 PM
08-24-2006 04:58 PM
NIS problem..
Hi all,
Good morning.
In one of my hp workstation(c8000), i am getting following nis error.
btc6h007#./sbin/init.d/nis.client stop
stopping ypbind
stopping keyserv
btc6h007#./sbin/init.d/nis.client start
starting NIS CLIENT networking
starting up the rpcbind
rpcbind already started, using pid: 968
domainname blr
starting up the Network Information Service
starting up the ypbind daemon
ypbind will not use the server list available in the file /var/yp/binding//ypservers for binding purpose. Also if ypbind is invoked with -broadcast option, then -broadcast option is ignored.
/usr/lib/netsvc/yp/ypbind -ypset
calling ypset with 161.85.20.25
Checking NIS binding.
Bound to NIS server using domain blr.
starting up the keyserv daemon
/usr/sbin/keyserv
btc6h007#ps -ef |grep ypbind
root 3305 2818 1 10:24:23 pts/ta 0:00 grep ypbind
root 3291 1 0 10:23:47 ? 0:00 /usr/lib/netsvc/yp/ypbind -ypset
Thanks in advance..
Regards,
srinu.
Good morning.
In one of my hp workstation(c8000), i am getting following nis error.
btc6h007#./sbin/init.d/nis.client stop
stopping ypbind
stopping keyserv
btc6h007#./sbin/init.d/nis.client start
starting NIS CLIENT networking
starting up the rpcbind
rpcbind already started, using pid: 968
domainname blr
starting up the Network Information Service
starting up the ypbind daemon
ypbind will not use the server list available in the file /var/yp/binding/
/usr/lib/netsvc/yp/ypbind -ypset
calling ypset with 161.85.20.25
Checking NIS binding.
Bound to NIS server using domain blr.
starting up the keyserv daemon
/usr/sbin/keyserv
btc6h007#ps -ef |grep ypbind
root 3305 2818 1 10:24:23 pts/ta 0:00 grep ypbind
root 3291 1 0 10:23:47 ? 0:00 /usr/lib/netsvc/yp/ypbind -ypset
Thanks in advance..
Regards,
srinu.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2006 06:13 PM
08-24-2006 06:13 PM
Re: NIS problem..
Hi Srinu,
What exact error are you referring to? I don't see any error here. I see that you're forcing the NIS client to bind to a specific server because you're starting ypbind with the -ypset option and giving it an IP address of one specific server to bind to.
The messages I see in your output are informational only, saying the list of server in the ypservers file will be ignored because you're using the ypset option.
It sounds to me like someone went to the trouble of creating a prioritized list of NIS servers by running the "ypinit -c" command and specifying the NIS servers to bind to, but you're ignoring that list of servers and telling this NIS client to only bind to 161.85.20.25.
Again, I don't see this as an error but more as informational. If you don't want to see these messages, and you want to use the list of servers in the ypservers file then you can modify your /etc/rc.config.d/namesvrs file and remove the "ypset" option from the YPBIND_OPTIONS variable and unset the YPSET_ADDR variable. That should allow the client to once again use the server list in the ypservers file.
If I'm misunderstanding your question please clarify exactly which message you're concerned about.
Regards,
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
What exact error are you referring to? I don't see any error here. I see that you're forcing the NIS client to bind to a specific server because you're starting ypbind with the -ypset option and giving it an IP address of one specific server to bind to.
The messages I see in your output are informational only, saying the list of server in the ypservers file will be ignored because you're using the ypset option.
It sounds to me like someone went to the trouble of creating a prioritized list of NIS servers by running the "ypinit -c" command and specifying the NIS servers to bind to, but you're ignoring that list of servers and telling this NIS client to only bind to 161.85.20.25.
Again, I don't see this as an error but more as informational. If you don't want to see these messages, and you want to use the list of servers in the ypservers file then you can modify your /etc/rc.config.d/namesvrs file and remove the "ypset" option from the YPBIND_OPTIONS variable and unset the YPSET_ADDR variable. That should allow the client to once again use the server list in the ypservers file.
If I'm misunderstanding your question please clarify exactly which message you're concerned about.
Regards,
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2006 11:56 PM
08-24-2006 11:56 PM
Re: NIS problem..
Hi,
No error in your logs.
See http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1052546&admit=-682735245+1156506597029+28353475
for ypbind with ypset options
Rgds
JMB
No error in your logs.
See http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1052546&admit=-682735245+1156506597029+28353475
for ypbind with ypset options
Rgds
JMB
Si vous ne faites jamais de bétises, c'est que vous ne faites rien de difficile. Et ça c'est une grosse bétise.
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