Bug 48425

Bug: 48425

Impact:

Product:

GemStone/S 64 Bit

Versions:

3.7.1, 3.7, 3.6.8, 3.6.7, 3.6.6, 3.6.5, 3.6.4, 3.6.3, 3.6.2, 3.6.1, 3.6, 3.5.8, 3.5.7, 3.5.6, 3.5.5, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5, 3.4.5, 3.4.4, 3.4.3, 3.4.2, 3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.2, 3.3.1, 3.3, 3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.x, 2.4.8, 2.4.4.8, 2.4.4.7, 2.2.6.5, 2.x

Platform:

Fixed In:

Remote log file naming using #log: NRS directive should include executable and pid

When logging in remotely, with the Gem on a node other than the Stone's node, a remote cache is started, and in additon to the Gem, a number of other processes are started up on the Gem and Stone nodes.  If the NRS for the Gem includes the #log: directive, which specifies the name of the log file, this pattern is also used for the log files for these other processes.

If the #log: directive argument does not include the %N pattern (the executable, such as gemnetobject or pcmon), and the $P pattern (the PID of the process), then, depending on the version, the process log files may be located in the home directory, rather than the intended directory, have default names rather than names following the log pattern; and/or process log files may have a trailing descriptive, such as .log_pcmon.

Workaround

When logging in remotely, ensure that any #log: directives in the Gem NRS or GEMSTONE_NRS_ALL includes both %P and %N.