[Evolution] Moving settings between computers
Dan Stromberg
strombrg@dcs.nac.uci.edu
Thu, 02 Dec 2004 12:14:08 -0800
--=-9jsDQI+qYLrXpqPYbZya
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Thu, 2004-12-02 at 18:59 +0100, guenther wrote:
> On Wed, 2004-12-01 at 18:18 -0800, Dan Stromberg wrote:
> > On Wed, 2004-12-01 at 23:05 +0100, guenther wrote:
> > > > I have Evolution on my home computer with several (6+) accounts on =
it,
> > > > and lots of offline folders, as well as some filters. I'd like to
> > > > transfer this information over to my work computer without having t=
o
> > > > re-add all the accounts and filters and settings manually, but can'=
t
> > > > seem to get it to work. If I copy over my ~/.evolution directory a=
nd
> > > > my ~/.gconf/apps/evolution directory to my work computer and run
> > > > Evolution I still get the First-Run Assistant.
> > >=20
> > > You will need to stop Evolution backend tasks and the GConf daemon
> > > before copying your data. On *both* machines (syncing the data to dis=
k
> > > on the source machine and not using old data on target machine):
> > >=20
> > > $ evolution --force-shutdown
> > > $ gconftools-2 --shutdown
> >=20
> > This is a valuable tip... but... what are you supposed to do if you hav=
e
> > to copy 10,000's of users from one NFS server to another, and you don't
> > have access to all of the NFS clients, and no reliable way of getting i=
n
> > touch with all of the users?
>=20
> Uhm, this question isn't Evolution nor GConf specific...
>=20
> You are in trouble, sure. But you are always in trouble, when doing
> this. Moving a lot of data and switching machines cannot be done, while
> users are still accessing and modifying the data on the source machine.
>=20
> You are trying to move $HOME directories for thousands of users? Then
> you need to make sure, no user is modifying his data while moving.
> Otherwise, he might end up with data loss. You are allowing the users to
> sort mails using procmail? Oh, then your MTA is accessing data in $HOME
> as well. Likewise for any other app...
>=20
> Yes, "downtime" is a nasty word... ;-)
I'm aware that problems can come from moving a bunch of $HOME's with
active users, but from this discussion I've inferred rightly or wrongly,
that gconf+evolution have changed this from a "look out for race
conditions" problem to a "problems every time" scenario.
I am worrying about nothing? Or has the situation truly gotten worse?
--=-9jsDQI+qYLrXpqPYbZya
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQBBr3eQo0feVm00f/8RAuudAJ0ZPz8MybI25ZArtQ/qfkGfWSirhwCfWqjU
Dto0UGb8toZCWb4eTxJP0E8=
=MwZd
-----END PGP SIGNATURE-----
--=-9jsDQI+qYLrXpqPYbZya--