Process Parameters Entries

The Registry path that contains entries for the SunLink Server Process Parameters is as follows:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AdvancedServer\ProcessParameters

• CoreOk REG_DWORD 0 or 1

  Specifies whether the server can create a core dump file on disastrous failures.

  Default: 0 (do not create core file)

• KeepSpareServer REG_DWORD 0 or 1

  Specifies whether the server should have a spare lmx.srv process available for another client. New client connections are likely to be quicker if this key is enabled.

  Default: 1 (start lmx.srv process)

• LockNapInMSec REG_DWORD 1 - infinity

  Specifies the length of time in milliseconds that the server sleeps when shared memory lock contention occurs. The server retries busy locks at intervals specified in this key until the length of time specified in the value of the MaxLockTimeInSeconds key elapses.

  Default: 10 milliseconds

• MaxLockTimeInSeconds REG_DWORD 5 - infinity

  The maximum interval in seconds that a server process waits for a shared memory lock to become available.

  Default: 300 seconds (5 minutes)

• MaxVCPerProc REG_DWORD 0 - 101

  The maximum number of virtual circuits that each lmx.srv process should be able to handle. This limit normally is calculated on the fly by SunLink Server software using the value of the VCDistribution Registry key and the value of the maxclients parameter in the lanman.ini file. If the value of this key is non-zero, its value is used instead of the calculated value.

  Default: 0 (Use value of VCDistribution key)

• MaxVCs REG_DWORD

  The maximum number of virtual circuits that can be established to a SunLink Server computer. This key permits administrators to manually override the sizing of shared memory.

  Do not change the value of this key.

• MinSmbWorkerTasks REG_DWORD

  Determines how many SMBWORKER tasks are preallocated by lmx.srv processes on startup. Do not change the value of this key.

• MinVCPerProc REG_DWORD

  The minimum number of virtual circuits that each lmx.srv process should be able to handle. This limit normally is calculated on the fly by SunLink Server using the value of the VCDistribution Registry key and the value of the maxclients parameter in the lanman.ini file. If this value is non-zero, its value is used instead of the calculated value.

  Default: 0 (Use value of VCDistribution key)

• NumCIStructs REG_DWORD

  Sizes the CLIENTINFO array in shared memory.

  Do not change the value of this key.

• NumCLIENT_SESSION REG_DWORD 5 - 128

  Limits the number of trust relationships that a server can maintain with other domains. This figure should be at least one greater than the number of domains trusted by the server's domain.

  Default: 5

• NumHashTables REG_DWORD 8 - infinity (powers of 2)

  The number of buckets for the hash table in shared memory to keep track of the various modes that clients have used to open files and set record locks.

  Do not change the value of this key.

  Default: 128

• NumSERVER_SESSION REG_DWORD 5 - infinity

  Limits the number of servers and Windows NT clients that can authenticate with the server. This figure should be large because it limits the number of Windows NT clients that can contact the server. On a primary domain controller, it must be at least the number of servers and Windows NT clients in the domain.

  Default: 100

• NumUStructs REG_DWORD 1 - infinity

  The number of structures allocated in shared memory to handle record lock and open file records. The sum of open files and record locks cannot exceed the value of this key.

  Default: 1000

• SpareServerTime REG_DWORD 0 - infinity

  The interval in seconds that a spare lmx.srv process is allowed to run without serving a client before being terminated.

  Default: 120 seconds (2 minutes)

• StopOnCore REG_DWORD 0 or 1

  Specifies whether the lmx.ctrl process is to stop if it finds that an lmx.srv process has terminated unexpectedly.

  Default: 0 (do not stop SunLink Server)

• VCDistribution REG_MULTI_SZ List

  Specifies the distribution of virtual circuits or sessions over lmx.srv processes. The architecture of the server allows multiple sessions to be served by each lmx.srv process on the Solaris system. The server must decide if a new session should be handed off to an existing lmx.srv process or if a new process should be started. This key specifies the distribution of sessions over the lmx.srv processes.

  Values are entered in sets of three integers separated by commas, each set of three numbers on a new line. In each set, the first number specifies the number of clients; the second is the minimum number of virtual circuits each lmx.srv process should support; the third is the maximum number of virtual circuits each process should support.

  Default: 1,2,12

  20,2,20

  35,2,24

  50,3,28

  85,4,28

  100,5,32

  130,6,36

  180,8,42

  250,9,44

  350,10,50

  500,10,60

  750,10,80

  1000,10,101

The following table describes the meaning of the default values.

Table A-5 lmx.srv Processes Default Value Meaning

Client Range	Min. Sessions per lmx.srv	Max. Sessions per lmx.srv
1-19	2	12
20-34	2	20
35-49	2	24
50-84	3	28
85-99	4	28
100-129	5	32
130-179	6	36
180-249	8	42
250-349	9	44
350-499	10	50
500-749	10	60
750-999	10	80
1000+	10	101