|
[SharedMemory
Access] |
Description
|
Factory value
|
Access mode
|
|---|---|---|---|
|
MaxSharedMemorySize
|
Maximum total size (in bytes) of the shared memory area used by solidDB.
Follow the value with K (to specify a value in KB), M (to specify a value in MB), or G (to specify a value in GB).
If the SMA server tries to allocate more memory, an "out of memory" error occurs.
If set to 0, the maximum total size is the same as the physical memory of the computer (platform specific).
Note The value that is set with the MaxSharedMemorySize parameter takes precedence over the value that is set with any corresponding kernel parameter (for example, SHMALL in Linux environments). Thus, the value that is set with the MaxSharedMemorySize parameter must not be higher than the value that is set with the corresponding kernel parameter.
If you set a non-default value for the MaxSharedMemorySize parameter, do not set a non-default value for the Srv.ProcessMemoryLimit parameter.
|
0
|
RW
|
|
SharedMemoryAccessRights
|
Validation context for the user access to the shared memory area.
The validation context is modeled after a traditional file validation mask. The possible values are:
▪ user – access is granted only to the same user as the one that started the SMA server
▪ group – access is granted to any user belonging to the same group as the one that started the SMA server
▪ all – access is granted to all users
|
group
|
RW
|
|
SignalHandler
|
If set to yes, the SMA driver signal handler handles the signals that are defined with the Signals parameter.
The SMA driver signal handler enables the SMA system to survive the most common application failures, such as killing or interrupting the applications from outside, or when one of the application threads runs within the server code, and another thread that is running application code causes the application to crash.
Upon the capture of certain signals, the signal handler closes the SMA connections safely and exits the SMA application. In most cases, the SMA server continues to run despite abnormal application exits.
The SMA driver signal handler installs itself when the first SMA connection is established and uninstalls itself when the last SMA connection is closed. Previously installed signal handlers are retained.
|
yes
|
N/A
|
|
Signals
|
Signals that can break the SMA connection (handled by the SMA driver).
The signals are defined as integers or with the following mnemonics: SIGSTOP, SIGKILL, SIGINT, SIGTERM, SIGQUIT, SIGABORT.
If the SMA application loops outside of the SMA driver (for example, does not call any functions), the signal can fail to terminate the application. In such a case, complete the following steps:
1 Throw out the connections at the server.
admin command 'throwout userid'
2 Use the SIGKILL signal to force the SMA application to exit.
kill -SIGKILL pid
|
Linux and UNIX:
SIGINT, SIGTERM Windows:
SIGINT |
N/A
|