Tricking applications which bind to nodename only with libschost.so.1

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:

  1. Multihosted Data
  2. Host Names
  3. Multihomed Hosts
  4. Binding to INADDR_ANY as Opposed to Binding to Specific IP Addresses
  5. Client Retry

You can also read about analyzing the application for suitability.

For 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 hostname or 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.

Comments:

Post a Comment:
Comments are closed for this entry.
About

This Blog is about my work at Availability Engineering: Wine, Cluster and Song :-) The views expressed on this blog are my own and do not necessarily reflect the views of Sun and/or Oracle.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today