|
[SharedMemoryAccess]
|
Description
|
Factory value
|
Startup
|
|---|---|---|---|
|
MaxSharedMemorySize
|
This parameter sets the maximum total size of the shared memory area used by solidDB®.
If the SMA server tries to allocate more, an “out of memory” error occurs. With value “0”, the maximum value is set automatically to be the size of the physical memory of the computer (platform specific).
Note The value set with the SharedMemoryAccess.MaxSharedMemorySize parameter takes precedence over the value set with any corresponding kernel parameter (for example, SHMALL in Linux environments). Thus, the value set with the SharedMemoryAccess.MaxSharedMemorySize parameter must not be higher than the value set with the corresponding kernel parameter.
If you set the SharedMemoryAccess.MaxSharedMemorySize parameter, do not use the Srv.ProcessMemoryLimit parameter.
|
0 (automatic)
Unit: 1 byte, G=GB, M=MB, K=KB
|
RW
|
|
SharedMemoryAccessRights
|
This parameter sets a 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
|
The SignalHandler parameter controls the SMA signal handler functionality.
When set to yes, the SMA driver signal handler handles the signals 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 running application code causes 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
|
NA
|
|
Signals
|
This parameter defines the signals that can break the SMA connection and is handled by the SMA driver.
The signals are defined as integers or with the following mnemonics: SIGSTOP, SIGKILL, SIGINT, SIGTERM, SIGQUIT, SIGABORT.
Note 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:
1 Throw out the connections at the server.
admin command 'throwout <userid>'
2 Use SIGKILL signal to force the SMA application to exit.
kill -SIGKILL <pid>
|
Linux and UNIX: SIGINT, SIGTERM
Windows: SIGINT
|
NA
|
|
[SharedMemoryAccess]
|
Description
|
Factory value
|
Startup
|
|---|---|---|---|
|
SignalHandler
|
The SignalHandler parameter controls the SMA signal handler functionality.
When set to yes, the SMA driver signal handler handles the signals 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 running application code causes 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
|
NA
|
|
Signals
|
This parameter defines the signals that can break the SMA connection and is handled by the SMA driver.
The signals are defined as integers or with the following mnemonics: SIGSTOP, SIGKILL, SIGINT, SIGTERM, SIGQUIT, SIGABORT.
Note 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:
1 Throw out the connections at the server.
admin command 'throwout <userid>'
2 Use SIGKILL signal to force the SMA application to exit.
kill -SIGKILL <pid>
|
Linux and UNIX: SIGINT, SIGTERM
Windows: SIGINT
|
NA
|