On Aug 17 2007 09:47, Jim Sabatke wrote:

Jan Engelhardt wrote:

...

On Aug 17 2007 08:31, Jim Sabatke wrote:

...

I'm having somewhat the same problem as I reported a few weeks ago. Occasionally my home directory locks up on an 'ls'.

First question: does `ls -n` NOT hang in that case?

Yes, 'ls -n' does freeze the system.

The problem usually (to my memory) if not always happen when a message comes from any program using the RPM database. I get errors that the RPM database is in use by another program, or that the program is waiting for a lock on the RPM database. After that point, my system is fubar.

Also, lsof doesn't return anything, so I can't search for what is grabbing the RPM database, but I suspect a lot of the time it's the update program.

That sounds much like a kernel issue. Or bad hardware. Other thoughts would be processes in D state, or hung network mounts. Jan -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jan Engelhardt wrote:

On Aug 17 2007 09:47, Jim Sabatke wrote:

...

Jan Engelhardt wrote:

...

On Aug 17 2007 08:31, Jim Sabatke wrote:

...

I'm having somewhat the same problem as I reported a few weeks ago. Occasionally my home directory locks up on an 'ls'. First question: does `ls -n` NOT hang in that case? Yes, 'ls -n' does freeze the system.

The problem usually (to my memory) if not always happen when a message comes from any program using the RPM database. I get errors that the RPM database is in use by another program, or that the program is waiting for a lock on the RPM database. After that point, my system is fubar.

Also, lsof doesn't return anything, so I can't search for what is grabbing the RPM database, but I suspect a lot of the time it's the update program.

That sounds much like a kernel issue. Or bad hardware. Other thoughts would be processes in D state, or hung network mounts.

Jan

I finally got an lsof to work, and it looks like Beagle was attaching itself to the NFS mounts. BTW, it was a real PITA to get rid of Beagle; I had to go through a LOT of dependency fixes to get it off the machine, including a lot of gnome functionality. I haven't had a crash since I removed Beagle, but I don't think the system has been running long enough to really tell. Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 8/18/07, Jim Sabatke wrote:

...

I finally got an lsof to work, and it looks like Beagle was attaching itself to the NFS mounts.

This would only be the case if your NFS mount was in your home directory. Rather than uninstalling Beagle, you could tell it not to index those directories.

Just why does not beagle come with an opt-in strategy rather than opt-out? It's so disgusting... Jan -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org