Hi all. Just wondering why an attempt is made to run two instances of gconfd at the start of my gnome sessions. Here's my syslog: Dec 14 18:30:49 localhost gconfd (sebyte-3486): starting (version 2.8.1), pid 3486 user 'sebyte' Dec 14 18:30:49 localhost gconfd (sebyte-3489): starting (version 2.8.1), pid 3489 user 'sebyte' Dec 14 18:30:49 localhost gconfd (sebyte-3489): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gc\onfd-sebyte/lock/ior': probably another process has the lock, or your operating system has NFS file locking mis\configured (Resource temporarily unavailable) Dec 14 18:30:49 localhost gconfd (sebyte-3486): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" \to a read-only configuration source at position 0 Dec 14 18:30:49 localhost gconfd (sebyte-3486): Resolved address "xml:readwrite:/home/sebyte/.gconf" to a writa\ble configuration source at position 1 Dec 14 18:30:50 localhost gconfd (sebyte-3486): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" t\o a read-only configuration source at position 2 The second instance simply dies and the first is unaffected so I don't think it is causing any problems. Just wondering why it happens... Seb -- CC me by all means but a follow-up will usually do. _______________________________________________ gnome-list mailing list gnome-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gnome-list
