On Fri, 19 Mar 2004, Derrick J Brashear wrote: > > more recent .gconf problem that we have been seeing concerns the same lock > > file that needs to be removed before the user can launch a gnome session, > > but in this new case the lock file can't be removed unless the users home > > directory is salvaged. This latest problem seems to be connected with > > unclean fileserver restarts. > > Yes. And I'm still looking for a simple test case on this one. > (And I don't think it's "unclean" so much as "fileserver restarts", but > I'm guessing)
fwiw, I spent countless hours trying to write a reproducible test case for the gconf issue. I used code that I ripped directly from gconf. The plan was to be able to use cmdebug in conjunction with my program that could reproduce this problem. Despite many hours of trying, I only managed to reproduce the problem once and didn't have debugging turned on in the cache manager. I've since given up. I think Derrick hit the nail right on the head with, "run gconf on multiple machines and pray". Thanks, Dave -- Dave McMurtrie, Systems Programmer University of Pittsburgh Computing Services and Systems Development, Development Services -- UNIX and VMS Services 717P Cathedral of Learning (412)-624-6413 PGP/GPG Key: http://www.pitt.edu/~dgm/gpgkey.asc.txt _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
