Issue 102931 - The file change time check should be active even if file system locking is used.
Summary: The file change time check should be active even if file system locking is used.
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: DEV300m50
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.2
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-19 06:47 UTC by mikhail.voytenko
Modified: 2017-05-20 10:29 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mikhail.voytenko 2009-06-19 06:47:44 UTC 
Currently the time of the last document change is checked only if file system
locking is turned off. But it should be done even it is used, because the system
file locking does not work always in heterogeneous file systems.
Comment 1 mikhail.voytenko 2009-06-19 09:24:23 UTC 
fixed in fwk114
Comment 2 mikhail.voytenko 2009-07-08 15:25:40 UTC 
mav->tm: Please verify the issue. Possible scenario in our environment:
- store a document on Windows to your unix home drive ( do not close it )
- use Linux system to do "touch <filename>" command to change the timestamp
- change the document on Windows and store one more time
There should be a notification that the document has been already changed.
Comment 3 thorsten.martens 2009-07-20 12:05:51 UTC 
Checked and verified in cws fwk114 -> OK !