This appendix lists the environment variables used by GemStone/S 64 Bit. The list has two parts: variables intended for public use, and variables that are reserved for internal use.
The following environment variables are intended for use by customers. The variable GEMSTONE is required; the others may be useful in particular situations.
The location of the GemStone Object Server software, which must be a full path, beginning with a slash, such as /user3/GemStone-hppa.hpux.
The directory location for Admin Gem logs. By default, Admin Gem log files are created in the same directory as the Stone log, which is $GEMSTONE/data. You can set this environment variable to specify that Admin Gem log files are created in a different directory.
The location of an executable-dependent configuration file; see Creating an Executable Configuration File.
The location for the global GemStone logs and locks file, overriding the default /opt/gemstone/. This directory must already exist.
This directory controls visibility between GemStone processes, and must be the same for all GemStone processes that may want to interact with a given repository, including stone, gems, topaz, statmonitor, netldi, gslist, etc. GemStone processes that do not shared a common location for /gemstone/locks—either /opt/gemstone, /usr/gemstone, or a directory specified by $GEMSTONE_GLOBAL_DIR—operate as if they are in independent name spaces.
To keep a process’s log from being deleted when the process terminates normally, unset this variable in the appropriate script, such as $GEMSTONE/sys/gemnetobject.
Set to a list of colon-separated directories containing SSL keys and certificates, for use by copydbf -V.
Specifies the directory for the gem and gem dynamic libraries. This is primarily of use in debugging low-level problems, and is used by the gemnetdebug script to specify the slow gem and gem dynamic libraries.
The location of system log files for the Stone repository monitor and its child processes. For further information, see GemStone Process Logs.
Limits the number of file descriptors requested by a GemStone process. Normally, most GemStone processes raise their file descriptor limit from the default (soft) limit to the hard limit set by the operating system. Setting this variable to a positive integer sets a lower limit; a value of 0 disables attempts to change the default limit. This does not apply to the shared page cache monitor.
Sets a number of network-related defaults, including the type of user authentication that GemStone expects. For further information, see GEMSTONE_NRS_ALL.
The directory location for all Reclaim Gem logs. By default, Reclaim Gem log files are created in the same directory as the Stone log, which is $GEMSTONE/data. You can set this environment variable to specify that Reclaim Gem log files are created in a different directory.
If set to any value, this environment variable will cause tracing messages to be written to stdout for bind(), connect(), getaddrinfo() and related socket calls.
Internally, GemStone waits for five minutes for the shared page cache to start up and initialize. This environment variable overrides this timeout, and specifies the time, in seconds, that the Stone will wait for the shared page cache to startup before giving up.
The directory location for SymbolGem logs. By default, Symbol Gem log files are created in the same directory as the Stone log, which is $GEMSTONE/data. You can set this environment variable to specify that Symbol Gem log files are created in a different directory.
Location of a system-wide configuration file; see How GemStone Uses Configuration Files.
If defined, it should contain a date and time format string that overrides the GemStone LOCALE-based default. See Localizing timestamps in log files.
If GS_WRITE_CORE_FILE is defined, this is the number of seconds to wait before a catastrophically failing GemStone/S process writes a core file and terminates—by default, 60 seconds. To determine the cause of a problem, GemStone/S Technical Support needs a stack trace, which is usually written to the process log file prior to the process shutdown.
If you need to derive a stack trace directly from a failing (but not yet terminated) process by attaching a debugger to it, you can set this variable to increase the time available to attach the debugger.
If this variable is set to any value, PAM debugging information will be printed to stdout.
If this variable is set to any value, the shared page cache monitor process will print extra debugging to its log file.
In a slow or no-op build only, not available in normal (fast) builds for security reasons. If this variable is set to a directory, a process that logs in RPC will write output of SSL calls made during to a file named GsSslDebug_<pid>.log in the specified directory. This file may get very large.
At the end of each mark/sweep, if the percent of memory used is greater than the threshold specified by this variable, a SoftBreak (error 6003) is generated, and the threshold is raised by 5 percent. We suggest a setting of 75%.
The mark/sweep count at which to begin printing the Smalltalk stack at each mark/sweep.
For this and all other GS_DEBUG_VMGC_* environment variables, the printout goes to the "output push" file of a linkable Topaz (topaz -l) session, for use in testing your application. If that file is not defined, the printouts go to standard output of the session’s gem or topaz -l process.
The mark/sweep count at which to begin printing the C stack at each mark/sweep. This variable is very expensive, consuming 2 seconds plus the cost of fork() for each printout.
GS_DEBUG_VMGC_PRINT_MKSW
The mark/sweep count at which to begin printing mark/sweeps.
GS_DEBUG_VMGC_PRINT_MKSW_MEMORY
The mark/sweep count at which to begin printing detailed memory usage (20 lines) for each mark/sweep.
GS_DEBUG_VMGC_PRINT_MKSW_MEMORY_USED
Specifies when Smalltalk stack printing starts as the application approaches OutOfMemory conditions. At the end of each mark/sweep, if the percent of memory used is greater than the threshold specified by this variable, the mark/sweep is printed, the Smalltalk stack is printed, and the threshold is raised by 5 percent. In a situation producing an OutOfMemory error, you should get several Smalltalk stacks printed in the Gem log file before the session dies. The default setting is 75%.
The scavenge count at which to begin printing scavenges. Once this takes effect, all mark/sweeps will also be printed. Be aware that printing scavenges can produce large quantities of output.
The scavenge count at which to begin printing the Smalltalk stack at each scavenge. Be aware that this print activity can produce large quantities of output.
The scavenge count at which to begin printing the C stack at each scavenge. This variable is very expensive, consuming 2 seconds plus the cost of fork() for each printout.
Automatically call the primitive for System class>>_vmPrintInstanceCounts:0 when an OutOfMemory error occurs, and also print the Smalltalk stack. (For details about this method, see the comments in the image.) This applies to each Gem or linkable Topaz (topaz -l) process that you subsequently start.
The mark/sweep count at which to begin verifying object memory before and after each mark/sweep.
The scavenge count at which to begin verifying object memory before and after each scavenge. Once this takes effect, GS_DEBUG_VMGC_VERIFY_MKSW will also be in effect. Be aware that this activity uses significant amounts of CPU time.
Any value disables the loading of any customized Extended Character Set Character Data Tables. This feature is deprecated; see the Programming Guide for details.
A non-empty string disables the network keepalive facility. For further information about keepalive, see Disrupted Communications
A non-empty string disables a warning that GemStone is using /opt/gemstone instead of /usr/gemstone for log and lock files when both directories exist.Use of /usr/gemstone is only for compatibility with previous releases; the default location is /opt/gemstone.
When this environment variable is enabled in the environment for a gem process, by setting it to any value, this gem sessions will not attempt to handle a SIGSEGV, SIGBUS or SIGILL signal, but will shut down immediately. It will not generate a core nor print C stacks. This avoids side effects with user action or client Smalltalk code.
This can be set to UNIX-style date format string, to allow the output of the gslist utility to be displayed in a parse-able format.
When set, delete GemStone log files on clean exit; affects all processes except for Stone or NetLDI logs, which are never deleted. Logs for processes that exit with errors are not affected.
Ensure that no GemStone process log files are deleted, overriding any individual process settings for GEMSTONE_KEEP_LOG.
If this variable is set, if a remote cache page server becomes stuck, the page manager will request that the remote cache page server print its call stack to its log file.
Sets the size of the socket send buffer for the socket between the Gem and GCI client for an RPC Gem.
Sets the size of the socket receive buffer for the socket between the Gem and GCI client for an RPC Gem.
By default, core files are not created when a fatal error occurs. (The C level stack trace is written to the process log file prior to the process shutdown.) You can set this environment variable if you need a core file.
The location for log files produced during the upgrade of a repository for a new version of GemStone.
The following environment variables are reserved for internal use. Customers should not define these variables for use with GemStone unless specifically instructed to do so. Please refrain from using these variables for other purposes.