ubuntuone-preferences and ubuntuone-login both wait for CredentialsFound signal (in Lucid).
Both processes will interact with couchdb upon receiving of the signal, the first one will read replication exclusion, the latter will put a pairing record to the db.
It turns out that they are running so head-to-head that they initialize 2 desktopcouches. Desktopcouch checks the pid and if it is not there it will start the couchdb, however, since there are 2 simultaneous calls both processes start their own couchdb. Eventually only one pid will be written to the file, and only one couchdb will be contacted (because of dbus response being returned only by one desktopcouch instance)
ubuntuone- preferences and ubuntuone-login both wait for CredentialsFound signal (in Lucid).
Both processes will interact with couchdb upon receiving of the signal, the first one will read replication exclusion, the latter will put a pairing record to the db.
It turns out that they are running so head-to-head that they initialize 2 desktopcouches. Desktopcouch checks the pid and if it is not there it will start the couchdb, however, since there are 2 simultaneous calls both processes start their own couchdb. Eventually only one pid will be written to the file, and only one couchdb will be contacted (because of dbus response being returned only by one desktopcouch instance)