Bug 499729 - Create a Lock File when running KMM
Summary: Create a Lock File when running KMM
Status: RESOLVED DUPLICATE of bug 475674
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: git (master)
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-09 20:45 UTC by Brendan
Modified: 2025-03-25 12:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brendan 2025-02-09 20:45:23 UTC
I use KMM on various systems and I sync my KMM data file in real time with Syncthing. This can cause problems if I forget that it's open on one system when I open it on a different system.

To get around this, I run KMM using a bash script that checks for the presence of a lock file named "MyFileName.kmy.lock". 

If the lock file is present, my script reads the hostname from the lock file and uses zenity to open a dialog box telling me that KMM is already open on the hostname stored in the lock file and it does NOT run KMM.

If the lock file is not present, my script creates the lock file and copies the hostname into the lock file. When KMM closes, the lock file is removed.

It would be nice if this functionality was all handled by KMM. It could be turned on and off in the KMM settings since some people may prefer it the way it is today.
Comment 1 Thomas Baumgart 2025-03-25 12:21:38 UTC
*** This bug has been marked as a duplicate of bug 475674 ***