gconfd strangeness ... (workaround)

[Michael Meeks <michael ximian com>]

	It seems something extremely odd has happened to my gconfd; at
least my system was virtualy unusable and I accumulated:

[michael michael gconf]$ ls -l ~/.gconfd/saved_state
-rwx------    1 michael  michael  157701248 Mar  9 14:12 /tmp/saved_state

	Which as you might imagine took a considerable time to process on
gconfd startup.

	How it got in that state I have no idea, but either way the
workaround is to kill gconfd-2 and kill that file.

	Worse - the file seems to be chock full of fairly valid data from
lots of users, no instances of millions of repeats that I can see.

	HTH someone,

		Michael.

-- 
 mmeeks gnu org  <><, Pseudo Engineer, itinerant idiot

_______________________________________________
gnome-hackers mailing list
gnome-hackers gnome org
http://mail.gnome.org/mailman/listinfo/gnome-hackers