Thomas Viehmann <[EMAIL PROTECTED]> writes:
> Derek Atkins wrote:
>> See, this is absolutely a requirement, IMHO. If gconf2 doesn't let us
>> do this then, IMHO, we CANNOT use gconf2. I consider it a
>> 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), then settings will be shared across the
> network and written by the first gconfd activated by the user, assuming
> $HOME is shared.
> I'm not exactly an expert, though.
In my case $HOME is shared, but nothing else is. So long as user-data
is stored in $HOME then that's usually sufficient. I just absolutely
need to be able to logout from machine 1, login to machine 2, and be
able to access gnucash the same on both machines.
> Cheers
>
> T.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
