thomas graichen wrote:
>
> Simon Matter <simon.matter@xxxxxxxxxxxxxxxx> 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 <tgr@xxxxxxxxxxx> ... 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
I've noticed that the problem isn't that the .ICEauthority-* files are
still there, it is because it claims it can't lock the files. This is
why I suggested a while back that whenever a filesystem recovery occurs,
if flags are present in the filesystem that mark files that are already
locked, they should be cleared. Apparently there is no flag preserved by
the filesystem, at least not relevant to fcntl (does the kernel keep a
list of locks in ram?).
D. Stimits, stimits@xxxxxxxxxx
|