Multi-user gnucash

linas@linas.org linas@linas.org
Fri, 23 Mar 2001 11:32:18 -0600 (CST)


It's been rumoured that Rich Shepard said:
> 
> > Thinking about this a little more, I think all you need is the shell
> > (actually more like perl or C) wrapper.  You will need a parent directory
> > for your project, which has read/write/execute permissions for the GROUP
> > of people working on the project. You probably need SGID set on that
> > directory as well, something like 2770 for permissions on that parent
> > directory.
> 
>   You've lost me totally. What project? What are we to wrap, and why should
> this be done? Linux is inherently multi-user (both peer-to-peer and
> client-server). We use (or try to, at least) gnucash for personal finance.
> But, rather than having both of us work on one machine, my wife invoked
> gnucash from her networked workstation by telnet'ing to the workstation on
> which the software is installed. When we clear the LCK and LNK files from
> the shared data directory, it runs just fine. But, when she exits the
> program (or, when I exit the program if I'm running it from a networked
> box), the LNK and LCK files are not removed.

How do you exit gnucash?  Do you use the main gnucash
pulldown menu and select "exit" from that menu?  Or do you use the
window manager to close the main gnucash window?

If its the latter, then I suspect that maybe the window manager isn't
ICCCM compliant, and so gnucash doesn't receive the shutdown message...
or something like that.  On the telnetted machine, can you 
ps ax |grep gnucash
and verify that gnucash has exited?  If closing the main window didn't
cause gnucash to exit, then of course the lock files wouldn't be
removed ...

If gnucash does exit, then could you run 'gdb /usr/bin/gnucash' and 
then type 'r' at the gdb prompt; and proceed as normal.  Then, when you
exit gnucash, does gdb say 'exited normally', or does it say 'received
signal SIGPIPE' or something like that?

I remember your compaining about this bug a year ago, so I'd like to 
see it resolved ...

--linas