03567: | Reggie won't start when ContainerManager run by multiple Unix users |
Category: Integration
Status: ClosedSeverity: HIGH
Reported against release: 0.8
Fixed in release: 0.8.1 (Beta Refresh)
PROBLEM:On UNIX machines, reggie will not start when multiple users try to run
the container manager (ow.sh):
"just this morning I found out that unless I removed the reggie-log
directory (which belonged to someone else), so that a new one could be
created, nothing seemed to work." ANALYSIS:Unfortunately, there isn't a fix for this problem, only a workaround.
Reggie always requires a log file be specified on startup, whether its
running in "transient" or "activatable" mode. There is no way to change
this short of making code changes to Reggie.
When Openwings is run on a multi-user machine, the intent was that only
one user would run the core, including Reggie. The workaround for this
problem is to create an administrative account for Openwings and use
this login to run the core.
Another possible workaround would be to have users change their
configurations to specify different temp directories so they would not
be attempting to overwrite each other's log files, but this would be
pretty messy.
The release notes should be updated to reflect the suggested workaround. WORKAROUND:Install Openwings under its own account.
|
