Opened 13 years ago
Last modified 10 years ago
#1120 new enhancement
IZ179: make sure changes to global testsuite config files do not overwrite more recent versions
Reported by: | joga | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | testsuite | Version: | current |
Severity: | Keywords: | framework | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=179]
Issue #: 179 Platform: All Reporter: joga (joga) Component: testsuite OS: All Subcomponent: framework Version: current CC: None defined Status: NEW Priority: P3 Resolution: Issue type: ENHANCEMENT Target milestone: milestone 1 Assigned to: issues@testsuite QA Contact: joga URL: * Summary: make sure changes to global testsuite config files do not overwrite more recent versions Status whiteboard: Attachments: Issue 179 blocks: Votes for issue 179: Vote for this issue Opened: Tue Mar 11 09:18:00 -0700 2008 ------------------------ When making modifications to the global testsuite configuration files (host config, user config, database config), it can happen, that someone else also modified such a file in the meantime, esp. when entering the configuration menu in a testsuite that is already running for some time. The probability of such a race condition can be limited, by - rereading the configuration before entering the configuration dialog - before writing, make sure the file hasn't be modified in the meantime
Note: See
TracTickets for help on using
tickets.