[GNC] Configuration dilemma -- How best to share Gnucash between 2 users

[Chris Mitchell]

Keeping the data files on shared network storage ("Windows network
share", Samba, NFS, sshfs, etc) and accessing them directly has the
advantage of real-time file locking: If a running instance of Gnucash
has the data file open, then when you try to open it from another
Gnucash instance on another machine, it pops up a dialog warning you
that the file is already in use.

I much prefer this setup, because it effectively prevents the
"accidentally edit both" scenario. No remembering to run a sync
process, no copies to get out of sync, no manually copying edits from
your out-of-sync copy (and hopefully not missing any)... Just one file,
which you *can* edit if it's not currently in use, and *cannot* edit if
it is.

Cheers!
 -Chris


On Tue, 10 May 2022 09:50:37 -0600
John Griessen <john at industromatic.com> wrote:

> On 5/9/22 11:07, Derek Atkins wrote:
> > The main gotcha is that only one person can have the data file open
> > at a time.  This means you will need to coordinate "who is running
> > GnuCash" at any particular moment.  
> 
> 
> I use gnucash on two linux machines with a sync program called unison
> keeping the data files up to date on each.  I run unison before
> switching machines.  This has to be a hard and fast rule or time will
> be wasted when you accidentally add new data to each instance.
> 
> If you accidentally edit both, you manually copy what was done on
> one, then abandon it with the next sync.
> _______________________________________________ gnucash-user mailing
> list gnucash-user at gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> ----- Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.



--