On Wed, Jul 15, 2026 at 11:34 AM David G. Pickett via gnucash-user < [email protected]> wrote:
> It occurred to me that, once a save has been completed, gnucash could > delete the lock file. This would allow either another user of networked > files or a botch run for finance quotes to update the file. If the running > original gnucash goes to modify his memory or display a new page or report, > a flag can tell it that it deleted the lock, and so check the age of the > file Mulling it over... * How often should it check for the presence of the lock file? Seems like checking the file system before every action could drag down responsiveness. (And if too infrequently, and you'll make a change not knowing the lock file has been created.) * When checking file "age" I assume it would use a time stamp? What happens if the different computers don't have their clocks synchronized? I've even had time stamp craziness on a single computer when dual-booting 2 OS's...one assumes the time on the BIOS clock was local, and the other assumes BIOS is UTC, so they were hours off. -- *Jim * _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
