search for: 131051

Hi all, Just watching for my first time the 'oom-killer' call in a CentOS 4.2 workstation. System was running normally but with high load of nice process, iow, rosetta and seti, others appart, nautilus, etc... i realized that after a night of standby running normally, the next moorning after few manual operations from X-session in local console, it started a massive swapping, this time

The way some DBs work is by having a separate lock monitor thread that runs every few seconds. This thread inspects a list of waiting locks for any cycles, which would indicate a circular relationship between processes holding locks & processes waiting for locks. The db then chooses a victim & kills one of the processes. (See "Inside MS SQL Server" by Delaney, pp778 for