On Sun, Jun 20, 2004 at 07:26:56PM +0200, Thomas Viehmann was heard to remark: > Derek Atkins wrote: > > show-stopper if you tie a user's gnucash configuration to a single > > machine. I'd rather keep the existing scheme-based configuration than > > lose the ability to have the same desktop on multiple machines (I > > already have this feature in my environment). > > AFAIU, networking needs to be enabled in /etc/orbitrc (which it isn't by > default at least in Debian),
Network security fears ... > then settings will be shared across the > network and written by the first gconfd activated by the user, assuming > $HOME is shared. It would be seriously cool if gconf was distributed, so that, e.g. when machine 2 shows up on net, its gconf would sync with that from machine1. After sync machine1 could be shut down, or whatever ... machines could come & go, join the party & leave... the data would persist. As a side note, corba does have this 'service discovery' feature, this thing where you can ask "who holds the gnucash config data" and there would come this response "oh, machine 10.0.0.1 holds it", so the user does not need to specify any explicit machine name for the service. I have no idea if gconf uses this, it would be cool if it did. --linas -- pub 1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <[EMAIL PROTECTED]> PGP Key fingerprint = 8305 2521 6000 0B5E 8984 3F54 64A9 9A82 0104 5933 _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
