[ http://issues.apache.org/jira/browse/GUMP-50?page=all ]
Leo Simons closed GUMP-50:
--------------------------
Resolution: Fixed
Fix Version: Gump3-alpha-3
(was: Gump3-alpha-5)
Gump3 uses a file-based lock coded in bash that's been tested on
linux/mac/windows and seems to work just fine.
> A portable/robust lock is needed (that the OS cleans up)
> --------------------------------------------------------
>
> Key: GUMP-50
> URL: http://issues.apache.org/jira/browse/GUMP-50
> Project: Gump
> Type: Bug
> Components: Python-based Gump
> Versions: Gump2
> Reporter: Adam Jack
> Fix For: Gump3-alpha-3
>
> A lock is required so two gump processes do not run at the same time, and
> conflict. The mechanism employed today is flawed in that the OS can not clean
> up the lock on process termination, so we get stray locks left around.
> P.S. Eventually we ought lock the workspace, and ensure that two workspaces
> can run simultaneously. Right now even that is not true, with use fo
> $GUMP/tmp.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
