Security Considerations
93
no
vd
ocx (
e
n)
1
1
Decemb
er
2
007
<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
/etc/opt/novell/bcc/bccsettings.xml
. It
should be noted that on linux this file might be overritten by BCC at any time. Therefore, any
changes to this file on linux will be ignored and lost. All changes should be made in eDirectory.
The following table provides additional information on each setting:
Table C-3
BCC XML Settings
Setting
Description
Default Value
<adminGroupName>
The name of the LUM enabled group BCC
uses on Linux.
bccgroup
<authorizationCacheTTL>
The number of seconds the authorization
rights are cached in the BCC OpenWBEM
provider.
300 seconds
This is not supported
until the first support
pack.
<cimConnectTimeout>
BCC CIM client connect timeout in seconds.
15 seconds
<cimReceiveTimeout>
BCC CIM client receive timeout in seconds.
30 seconds
<cimSendTimeout>
BCC CIM client send timeout in seconds.
30 seconds
<idlePriorityThreshold>
The number of idle high priority threads before
BCC starts killing priority threads.
3
<initialNormalThreads>
The number of normal threads created by
BCC.
3
<initialPriorityThreads>
The number of high priority threads created by
BCC at startup.
2
<ipcResponseTimeout>
The timeout in seconds that BCC will wait for
an IPC response.
15
<maximumPriorityThreads>
The maximum number of high priority threads
BCC will create.
20
<minimumPriorityThreads>
The minimum number of high priority threads
BCC will keep after killing idle high priority
threads.
2
<resourceOfflineTimeout>
The number of seconds BCC will wait for a
resource to go offline during a BCC migrate.
300
