[grisbi-bugs] [Grisbi 0001625]: Locking in /tmp is wrong

[Grisbi Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://www.grisbi.org/bugsreports/view.php?id=1625 
====================================================================== 
Reported By:                rainglasz
Assigned To:                
====================================================================== 
Project:                    Grisbi
Issue ID:                   1625
Category:                   Main
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
OS:                         Tous(All) 
Unstable Impact:            Yes 
Version OS:                 Wheezy and WinXP 
Version GTK:                 
====================================================================== 
Date Submitted:             2013-12-12 22:23 CET
Last Modified:              2013-12-12 22:45 CET
====================================================================== 
Summary:                    Locking in /tmp is wrong
Description: 
A lockfile is created in /tmp (or whatever TEMPDIR is) using the original
filename.
If a data file thus locked is accessed from a remote computer via a file share,
the lock is not honored.
Moreover, two users on a multiuser system using the same name for different data
files get locked out.

Steps to Reproduce: 
- Open grisbi file on Linux
- Open on different computer, e.g. Windows via SMB
- change in both
- save both 
- no lock message, data from the first is lost

Additional Information: 
The lockfile **must** be created in the directory where the datafile is.
====================================================================== 

---------------------------------------------------------------------- 
 (0003706) rainglasz (reporter) - 2013-12-12 22:45
 http://www.grisbi.org/bugsreports/view.php?id=1625#c3706 
---------------------------------------------------------------------- 
Best would be to write the PID to the lock file as to easily detect stale lock
files if there is not process with that PID. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2013-12-12 22:23 rainglasz      New Issue                                    
2013-12-12 22:45 rainglasz      Note Added: 0003706                          
======================================================================