- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: understanding fastbind(1)
Operating System - HP-UX
1748282
Members
4021
Online
108761
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-04-2005 04:06 AM
тАО07-04-2005 04:06 AM
Hi,
I try to understand fastbind(1). If I'm running it on some binary, it records some information within the binary (confirmed by doing a ls -l before and after the run). But, it does not show any effect. I tusc'd one process before and after fastbinding it and the trace showed exactly the same sequence of finding and loading the shared libraries. I expected that after fastbind only the actual shared libraries would be loaded.
What do I miss here?
Thanks for any clarifications.
BR
Stefan Hirsch
I try to understand fastbind(1). If I'm running it on some binary, it records some information within the binary (confirmed by doing a ls -l before and after the run). But, it does not show any effect. I tusc'd one process before and after fastbinding it and the trace showed exactly the same sequence of finding and loading the shared libraries. I expected that after fastbind only the actual shared libraries would be loaded.
What do I miss here?
Thanks for any clarifications.
BR
Stefan Hirsch
Solved! Go to Solution.
- Tags:
- fastbind
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2005 02:34 AM
тАО07-06-2005 02:34 AM
Re: understanding fastbind(1)
Stefan,
Did you try running "fastbind -n" (which removes all fastbind information) on the same executable and then run tusc to see if the dynamic loader search method changed?
Are the shared libraries system libraries (default HP-UX) or freeware libraries?
I'm guessing that fastbind is meant to optimize the speed at which the dynamic loader finds shared libraries. In my experience, it doesn't seem to resolve certain hit/miss searching in all cases. Especially when some shared libraries need to open other shared libraries as dependencies. Also, I think fastbind was designed for older systems back in the day when shared libraries took a long time to search and open...it may have dropped off the radar since those old days and perhaps lacks some functionality and intellegence?
I wish I knew more. Hopefully someone else who knows a bit about the internals of fastbind may know more and reply.
Did you try running "fastbind -n" (which removes all fastbind information) on the same executable and then run tusc to see if the dynamic loader search method changed?
Are the shared libraries system libraries (default HP-UX) or freeware libraries?
I'm guessing that fastbind is meant to optimize the speed at which the dynamic loader finds shared libraries. In my experience, it doesn't seem to resolve certain hit/miss searching in all cases. Especially when some shared libraries need to open other shared libraries as dependencies. Also, I think fastbind was designed for older systems back in the day when shared libraries took a long time to search and open...it may have dropped off the radar since those old days and perhaps lacks some functionality and intellegence?
I wish I knew more. Hopefully someone else who knows a bit about the internals of fastbind may know more and reply.
If it ain't broke, it needs optimized.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2005 02:43 AM
тАО07-11-2005 02:43 AM
Solution
fastbind records which library provides each symbol. It reduces the time required to do the lookup of each symbol string among the available shared libraries. It can have a significant effect for short duration executables that use many shared libraries with many shared symbols. Its benefit has been reduced by the implementation of +gst global symbol table option. The +gst option can also reduce the time spent resolving symbols. The +gst option has the advantage that is does not require rerunning any command when shared libraries are updated. You just need to use it when building libraries and excutables. (You can use it on just an exectuable, but get more improvement by using on shared libraries as well.)
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