[#RIO-165] Forked/Exec'd log location

Rio

Forked/Exec'd log location

Created: 26/Feb/09 01:45 PM Updated: 27/Feb/09 05:54 PM

Component/s:

Deployment

Affects Version/s:

4.0 M2

Fix Version/s:

4.0 M3

Time Tracking:

Not Specified

Description

« Hide

The log directory for forked/exec'd services should be configurable, and should be organized by opstring name. For example:

/<service-log-root>/services.log/<normalized-opstring-name>/service-name-<instance-id>

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Dennis Reedy added a comment - 27/Feb/09 05:54 PM

Forked service log files are stored in a location as follows:

/<serviceLogRootDirectory>/service_logs/<normalized-opstring-name>/service-name-<instance-id>

The serviceLogRootDirectory is a configuration parameter configured for the Cybernode (org.rioproject.cybernode.serviceLogRootDirectory), and defaults to the value returned by System.getProperty("java.io.tmpdir"). Forposix systems this equates to /tmp

This is the root directory to create service logs for services that are forked. This directory will be used as follows:

/<serviceLogRootDirectory>/service_logs/<normalized-opstring-name>/service-name-<instance-id>

If the serviceLogRootDirectory directory does not exist it will be created.
If the service_logs directory does not exist it will be created.
The normalized-opstring-name is the name of the service's OperationalString, with all " " converted to "_". If the normalized-opstring-namedirectory does not exist it will be created.
The service-name-<instance-id> is a file with the redirected output and error streams for the service. If the service name contains " ", they will be converted to "_"

This property is read each time a service is forked.

As an example, the first instance of the "Hello World" service in the "Hello World Example" opstring would have it's service log created in:

/tmp/service_logs/Hello_World_Example/Hello_World-1