Google Earth (on Linux) does some checking outside of supplied environment
variables in an attempt to ensure that only one instance is running. However,
creating a different user for each instance you wish to run, then giving those
users access to the local Xorg server will allow you to keep most of the
application confined to each user's home directory. The last variable is
lock/cache files within /tmp - which can be tricky to handle, but making the
files unavailable to these non-privilaged users or making /tmp a hidden
per-process temporary mountpoint both seem to work fine in our testing.
Outside of Google Earth, there is still the networking bit to consider - do you
broadcast to different ports, different netmasks, or unicast to a ViewSync
relay.
Some code is already committed to the code.google.com/p/liquid-galaxy project
which can help, so browse there and feel free to continue discussion.
Good Luck!
--
Kiel Christofferson
End Point Corporation
http://www.endpoint.com