Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8O6FM822142 for linux-xfs-outgoing; Sun, 23 Sep 2001 23:15:22 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8O6FHe22121 for ; Sun, 23 Sep 2001 23:15:18 -0700 Received: (qmail 14248 invoked by uid 8); 24 Sep 2001 06:15:13 -0000 From: thomas graichen Reply-To: thomas graichen X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: lock files after crash Date: Fri, 21 Sep 2001 22:25:20 +0200 Organization: spoiled dot org Lines: 22 Distribution: local Message-ID: References: <4.3.2.7.2.20010912091115.03368618@pop.xs4all.nl> <3B9F1B27.49261933@idcomm.com> <3B9F879E.3FB8976@ch.sauter-bc.com> Reply-To: thomas graichen X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.9-xfs (i686)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Simon Matter wrote: > At least you're not alone, I was having the same problem. Did you really > have a kernel crash? I don't rember what happened in my case but I > thought I was upgrading some RPM's and when I rebooted next time I just > couldn't login. IIRC I did not have a kernel crash. i observed something similar too - the reason why logging in is not really possible is the existence of some .ICEauthority-* files - simply removing them should fix the problem - so there is no magic here - the locking seems to be done pretty trivial via some kind of normal files t p.s.: i hope i got the content of the question correct - i'm trying to catch up the lists now and might have gotten something wrong - if so - please forgive me :-) -- thomas graichen ... perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. --- antoine de saint-exupery