running concurrent gnucashes with one database

[Adrian Mariano]

On Mon, Jan 18, 2016 at 01:46:27PM +0000, Colin Law wrote:
> On 18 January 2016 at 13:32, Adrian Mariano <radian at cox.net> wrote:
> > Unless I have a way of forcing it to quit from another machine
> > (e.g. logging in and running kill on it), this isn't enough to solve
> > the problem, really.  Can gnucash give up its lock if you click
> > "save" so that I could switch to a different invocation without
> > closing the first one?
> 
> As well as doing that it would have to prevent you making any changes
> until it had acquired the lock again.
> 

If it noticed that the lock was taken and went into read only mode
then that goal would be accomplished.