- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- remsh and /etc/nsswitch.conf
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО11-29-2001 06:44 AM
тАО11-29-2001 06:44 AM
When I switch the order in /etc/nsswitch.conf to NIS FILES DNS, remsh from host A to host B DOES work.
What I don't understand is why should I have to switch the order in /etc/nsswitch.conf if for example NSLOOKUP on host A DOES find host B in NIS even when I DON'T switch the order (i.e. the order is DNS, NIS, FILES and each service "continues" on to the next service) ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2001 06:57 AM
тАО11-29-2001 06:57 AM
Re: remsh and /etc/nsswitch.conf
This won't help, but what version of HP-UX are you using. I have exactly the same situation on a HP-UX 11.00 system so I am beginning to wonder if we have discovered a small undocumented feature (bug)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2001 07:07 AM
тАО11-29-2001 07:07 AM
Re: remsh and /etc/nsswitch.conf
[TRYAGAIN=continue]
How does the entry in nsswitch.conf looks like?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2001 07:10 AM
тАО11-29-2001 07:10 AM
Re: remsh and /etc/nsswitch.conf
Try using
DNS[NOTFOUND=continue UNAVAL=continue] NIS [NOTFOUND=continue UNAVAL=continue] files
in nsswitch.conf file.
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2001 07:16 AM
тАО11-29-2001 07:16 AM
Re: remsh and /etc/nsswitch.conf
I'm using hp/ux 11.0.
host A's /etc/nsswitch.conf is as follows.
hosts: dns [NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue] nis [NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue] files
Once again I'd like to mention that nslookup for a host that doesn't exist in DNS does find the host in NIS using the above configuration (like it should work), it's remsh'ing from host B that doesn't work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2001 07:33 AM
тАО11-29-2001 07:33 AM
Re: remsh and /etc/nsswitch.conf
I can't explain the NIS versus DNS behavior other than to use nslookup to retrieve the hostname by looking up the IP address and see what source nslookup got an answer.
My suggestion would be to use files first. Now the /etc/hosts file does not have to contain every IP address, only those that are important and frequently used. There is a major reliability advantage here: DNS and NIS servers must be extremely reliable as well as the routes to these servers.
If something goes wrong with NIS/DNS, exceedingly long delays (30+ seconds) will be incurred in all sorts of unexpected places, from backups (30 to 90 second delay per file!) to difficulties with 'r' commands that seem to hang (wait long enough and they get through), and so on. This can affect every computer on the network that uses DNS/NIS first.
And from a network load and overall performance point of view, having common IP addresses locally resolved can significantly improve performance in some cases. A good example is that most commercial network backup programs ask for host/IP information for every file...backup a million files and a million DNS/NIS requests will be issued.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2001 07:57 AM
тАО11-29-2001 07:57 AM
Re: remsh and /etc/nsswitch.conf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2001 07:57 AM
тАО11-29-2001 07:57 AM
Re: remsh and /etc/nsswitch.conf
As far as what you mentioned:
"I can't explain the NIS versus DNS behavior other than to use nslookup to retrieve the hostname by looking up the IP address and see what source nslookup got an answer."
I did an NSLOOKUP on the ip address for host A and DNS returned an obsolete name (i.e. the name returned was not host A but rather "xxxxx" - I guess the name that was originally assigned in DNS to the IP address but was never updated). Does this have anything to do with my problem ??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2001 08:02 AM
тАО11-29-2001 08:02 AM
Re: remsh and /etc/nsswitch.conf
As far as I know from man pages "services" has nothing to do with the procedure that remshd uses on the remote node, and I do not have any other line other that hosts in the /etc/nsswitch.conf file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2001 08:10 AM
тАО11-29-2001 08:10 AM
SolutionI also like files first and only put what's neccessary in /etc/hosts.
Darrell