I waited for up to 15 min and it didn't come back. What I realized is that famd had more than 20 files open in /afs. When I stopped fam, the freeze stopped and did not come back. But after the next reboot it was exactly the same thing.
I can consistently freeze my machine with the following steps: reboot log in with a user that has $HOME in /afs start terminal session enter su - <enter> <password> **freeze** Any idea what I can do to debug? I do not find anything useful in the logs (but perhaps I am just not looking at the right places or don't understand what might be useful). Am Mittwoch, den 06.08.2008, 15:12 -0700 schrieb Russ Allbery: > Felix Koop <[EMAIL PROTECTED]> writes: > > > No, it doesn't cause problems with reloading the module. I thought that > > would be the source of another problem I am having with my system, that > > is it freezes from time to time when I am using X as a normal user with > > my homedir in AFS and I thought that this might be related. But from > > your explanation it does not seem to be. > > Probably not. When it freezes, does it come back afterwards after a > delay, or does it stay frozen until you do something more aggressive? > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
