Comment 30 for bug 449760

I'll add my experience to this as well:

I had my .viminfo file (and other files) stored under the UbuntuOne directory (wasn't running Vim at the time), but experiencing 100% CPU usage by ubuntuone-syncd on one core. The log contained lots of entries like:

8db-4862-94b5-f747f1d3ded3 [root:8eef1216-51b4-41cd-9c20-235d8edfc494] ''Ubuntu One/.viminfo'' | Called calculate_hash (In: T:NONE:F)
2009-11-02 08:26:38,122 - ubuntuone.SyncDaemon.sync - INFO - T:NONE:F 9af352cb-88db-4862-94b5-f747f1d3ded3 [root:8eef1216-51b4-41cd-9c20-235d8edfc494] ''Ubuntu One/.viminfo'' | Called calculate_hash (In: T:NONE:F)
2009-11-02 08:26:38,123 - ubuntuone.SyncDaemon.sync - INFO - T:NONE:F 9af352cb-88db-4862-94b5-f747f1d3ded3 [root:8eef1216-51b4-41cd-9c20-235d8edfc494] ''Ubuntu One/.viminfo'' | Called calculate_hash (In: T:NONE:F)
2009-11-02 08:26:38,125 - ubuntuone.SyncDaemon.sync - INFO - T:NONE:F 9af352cb-88db-4862-94b5-f747f1d3ded3 [root:8eef1216-51b4-41cd-9c20-235d8edfc494] ''Ubuntu One/.viminfo'' | Called calculate_hash (In: T:NONE:F)

I killed off the daemon, and after examining the logs, moved my .viminfo back out into my home dir, removing it from the Ubuntu One directory. Reconnecting this time resulting in much more sane behaviour, it seemed to sync up, be happy about things and not use as much CPU in the process.

I've noticed that for some reason my .viminfo was owned by root (weird!), and I thus don't have permissions on it. I can well imagine that this might cause ubuntuone-syncd to thrash on it (although maybe it should act nicer about it).