在Redhat AS4上安裝了MySQL后，重啟后屏幕彈出幾個(gè)錯(cuò)誤對(duì)話框，而且整個(gè)UI環(huán)境為黑底，無菜單和按鈕，
其中錯(cuò)誤信息為：
Failed to contact configuration server; some possible causes are that
you need to enable TCP/IP networking for ORBit, or you have stale NFS
locks due to a system crash. See
http://www.gnome.org/projects/gconf/
for information. (Details - 1: IOR file '/tmp/gconfd-root/lock/ior' not
opened successfully, no gconfd located: No such file or directory 2:
IOR file '/tmp/gconfd-root/lock/ior' not opened successfully, no gconfd
located: No such file or directory)
出現(xiàn)問題的原因可能是某些配置出問題了，也有可能是系統(tǒng)本身出現(xiàn)了問題從而導(dǎo)致配置出錯(cuò)。
到
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, bad things may happen
to that user's preferences once in a while.
沒有發(fā)現(xiàn)解決問題的方法，后來發(fā)現(xiàn)，有為仁兄也碰到過類似問題，
解決方法為：
1.刪除當(dāng)前用戶在/tmp下的相關(guān)文件：
假設(shè)用戶名是root,就是這樣的#rm -R *root* 。
2.刪除用戶主目錄下的.gnome 和 .gnome2兩個(gè)文件夾。 假設(shè)用戶名是root,就是這樣的#rm -R /root/.gnome 和#rm -R /root/.gnome2.
3.重啟gnome環(huán)境，問題解決。