Bug 10665

Bug: 10665

Impact:

Product:

GemStone/S

Versions:

6.7.2.1, 6.7.2, 6.7.1, 6.7, 6.6.5, 6.6.4, 6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7.5, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.1.5, 6.1.x, 6.0.x, 5.1.5.1, 5.1.5, 5.1.4, 5.1.3, earlier versions

Platform:

Windows

Fixed In:

GemStone environment variables work differently for Windows services

The Windows NT/2000/XP services mechanism does not detect changes
to system environment variables until the system is rebooted.  As
a result, environment variables for services work differently
than they do for other processes.

Windows services disregard any value of GEMSTONE environment
variables.  Instead, they define their own GEMSTONE environment
variables based on their location on disk.

Workaround

Use the -v option to explicitly define the GEMSTONE environment
variable in the service's context.  If the -v option is used to
define GEMSTONE, that value will be used instead of the value
based on the location.  The -v switch can be entered as a
startup parameter in the Services option of Control Panel or as
part of the command line for a 'create' or 'start' operation.
For example:

stone create -v GEMSTONE_SYS_CONF=$GEMSTONE_SYS_CONF