Tricking applications which bind to nodename only with libschost.so.1
By tf on Jul 05, 2007
If you read through the Sun Cluster Data Services Developer's Guide for Solaris OS, you will find the requirements for non-cluster aware applications in Appendix E:
- Multihosted Data
- Host Names
- Multihomed Hosts
- Binding to
INADDR_ANYas Opposed to Binding to Specific IP Addresses
- Client Retry
You can also read about analyzing the application for suitability.
this blog number 2. is of special interest - if your application is
somehow depending on the physical node name of a server (ie. the name
that gets returned by
uname -n), and does not offer the possibility to configure to use a logical host name instead, than the libschost.so.1 library provided with Sun Cluster 3.2 might help you out.
The referenced man page has all the information needed with examples how to use it within C source and shell based agent code.
You can also find examples of its usage in the Open HA Cluster source code within the Oracle E-Business Suite and Oracle Application Server agent by using the search interface and browse through the results.