- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: libc.1 vs. libc.2
Operating System - HP-UX
1748171
Members
4269
Online
108758
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
Discussions
Discussions
Forums
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
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
тАО07-08-2004 05:02 AM
тАО07-08-2004 05:02 AM
One of our applications has run into a name resolution problem related to the different ways these libraries handle name resolution policies. The main problem seems to stem from the application being developed and compiled under 10.01, but run on 11.00. (My guess is that they don't want to develop on 11.00 because many customers still have 10.01 and 10.20 systems in production.) Changing the nsswitch.conf file to specify exactly what policy we want followed will work, but I'm wondering if there's anything the application developer can do to make the application behave as desired without this reconfiguration. On 11.00, libc.2, with the preferred behavior, exists and could be used, but it doesn't exist on 10.X (at least as the systems are patched). I'm guessing it's not possible, but, not being a programmer, just looking for confirmation.
--
Jeff Traigle
Jeff Traigle
Solved! Go to Solution.
- Tags:
- nsswitch.conf
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-12-2004 10:54 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-12-2004 11:00 AM
тАО07-12-2004 11:00 AM
Re: libc.1 vs. libc.2
Oops!
That 10.20 libc.2 comment left me with a bad feeling the moment I hit the 'submit' button.
Some joker put an 11.00 built libc.2 on the 10.20 system that I was just looking at. That should not be done and should not work.
You get libc.2 if you link on 11.00 or above.
That 10.20 libc.2 comment left me with a bad feeling the moment I hit the 'submit' button.
Some joker put an 11.00 built libc.2 on the 10.20 system that I was just looking at. That should not be done and should not work.
You get libc.2 if you link on 11.00 or above.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2004 12:49 AM
тАО07-13-2004 12:49 AM
Re: libc.1 vs. libc.2
Yeah. After much digging around online, I found enough information from various sources that everything crystalized and made sense regarding this issue. If you build to be compatible with 10.X, you have to set up the nsswitch.conf accordingly to force it to how 11.X resolves. Thanks.
--
Jeff Traigle
Jeff Traigle
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP