On Fri, Jul 12, 2002 at 03:54:34PM +0200, georges mariano wrote: > Bonjour � tous, > > J'ai nautilus qui fonctionne (apparemment) bien sur une woody. (donc > c'est faisable ;-) > > J'ai nautilus qui fonctionne pas du tout sur une autre woody > > Les deux machines sont cens�es �tre "similaires", avant de commencer > une exploration fastisidieuse et millim�triques des diff�rences, voici > les messages d'erreurs que je recois, au cas o� �a ferait tilt dans le > cerveau de quelqu'un ici ... > > bon, si je lance nautilus j'ai une palanqu� (jusqu'au Ctrl-C ;-) de : > > Eel-WARNING **: Erreur GConf : > Failed to contact configuration server (a likely cause of this is > that you have an existing configuration server (gconfd) running, but > it isn't reachable from here - if you're logged in from two machines > at once, you may need to enable TCP networking for ORBit) > > > dans les logs, j'ai �galement (toujours une palanqu� de) : > Jul 11 15:44:31 oryx gconfd (mariano-19905): Failed to get lock for > daemon, exiting: Failed to create or open > '/home/mariano/.gconfd/lock/ior' > > On en cause (un petit petit peu) sur Google mais c'est > incompr�hensible (pour moi).
J'ai eu ce genre de probl�me avec gconf sur un home directory mont� en NFS. Il arrivait pas � cr�er un lock, �a mettait le boxon. Ma solution barbare a �t� de faire un lien de .gconfd vers une partoche locale, mais c'est pas satisfaisant. Me semble que la solution propre est � trouver du c�t� des d�mons rpc.* (lockd, il me semble...) Hopla, 'tit coup de google: http://www.gnome.org/projects/gconf/ � I'm having a lock file problem. What do I do? Usually a problem here involves either NFS, or a kernel bug. The per-user daemon locks two files in the default configuration: ~/.gconfd/lock/ior ~/.gconf/%gconf-xml-backend.lock/ior The first lock is to ensure that only one gconfd is running. The second lock is to ensure only one program accesses the XML config source at a time. If you have an NFS-mounted home directory, you must be running an rpc.statd/rpc.lockd setup on both NFS client and NFS server, so that file locking works. On Red Hat Linux, this means the "nfslock" service must be running. Enable it permanently with the chkconfig tool - see its manual page. Turn it on or off at any given time with service nfslock start or service nfslock stop. You must be root to do this. If the kernel crashes (or the power cord gets pulled) on an NFS client machine, theoretically when you reboot the client machine it will notify the NFS server that it has rebooted and all previously-held locks should be released. However, many operating systems including Red Hat Linux 7.2 do not properly do this; so you will have stale locks after a crash. If no gconfd is running, these locks may safely be removed. If gconfd is running though, DO NOT remove them; if you have two gconfd processes for a single user, very bad things will happen to that user's preferences. � -- Manu // L'image est � l'objet qu'elle reproduit // comme l'opinion est � la science. // Platon, La R�publique, VI-510 a -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
