Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP1 - 9-21-2010 ADMINISTRATION GUIDE FOR OPEN ENTERPRISE SERVER 1 SP2 LINUX Administration Manual page 91

<cimReceiveTimeout>30</cimReceiveTimeout>
<cimSendTimeout>30</cimSendTimeout>
<idlePriorityThreshold>3</idlePriorityThreshold>
<initialNormalThreads>3</initialNormalThreads>
<initialPriorityThreads>2</initialPriorityThreads>
<ipcResponseTimeout>15</ipcResponseTimeout>
<maximumPriorityThreads>20</maximumPriorityThreads>
<minimumPriorityThreads>2</minimumPriorityThreads>
<resourceOfflineTimeout>300</resourceOfflineTimeout>
<resourceOnlineTimeout>300</resourceOnlineTimeout>
<scanForNewDevicesDelay>5</scanForNewDevicesDelay>
</bccSettings>
On Linux, the above XML is written to
noted that on Linux this file might be overwritten by Business Continuity Clustering at any time.
Therefore, any changes to this file on Linux are ignored and lost. All changes should be made in
eDirectory.
Table C-3 provides additional information on each setting:
BCC XML Settings
Table C-3
Setting
<adminGroupName>
<authorizationCacheTTL>
<cimConnectTimeout>
<cimReceiveTimeout>
<cimSendTimeout>
<idlePriorityThreshold>
<initialNormalThreads>
<initialPriorityThreads>
<ipcResponseTimeout>
/etc/opt/novell/bcc/bccsettings.xml
Description
The name of the LUM-enabled group that
BCC uses on Linux.
The number of seconds the authorization
rights are cached in the BCC OpenWBEM
provider.
BCC CIM client connect timeout in seconds.
BCC CIM client receive timeout in seconds.
BCC CIM client send timeout in seconds.
The number of idle high priority threads
before BCC starts killing priority threads.
The number of normal threads created by
BCC.
The number of high priority threads created
by BCC at startup.
The timeout in seconds that BCC waits for an
IPC response.
. It should be
Default Value
bccgroup
300 seconds
This is not
supported until the
first support pack.
15 seconds
30 seconds
30 seconds
3
3
2
15
Security Considerations 91