Subject: Fw: [Firebird-devel] Linux Lock Manager
To: None <email@example.com>
From: James K. Lowden <firstname.lastname@example.org>
Date: 03/04/2004 19:54:50
I have spent considerable time lately getting the Firebird database to
build on 1.6. Once I get it working, I'm hoping to package it.
Firebird "Classic" -- which I'm focussing on for now -- builds without
threads. There is also a threaded server, but I won't bother with that
until I upgrade to -current (or whatever our threaded kernel release is
called by then).
What advice I could give Mr. Starkey such that his lock manager would work
"out of the box" on NetBSD?
Begin forwarded message:
Date: Thu, 04 Mar 2004 12:20:42 -0500
From: Jim Starkey <email@example.com>
To: Firebird Devel <firstname.lastname@example.org>
Subject: [Firebird-devel] Linux Lock Manager
There are two ways to deliver lock manage blocking ASTs. Single
threaded platforms use signals, which requires a privileged process to
deliver signals across process groups. Multithreaded platforms using a
thread to monitor the lock table.
Why does the Linux lock manager use signals? Is there any reason not to
cut over to monitor thread?
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
Firebird-Devel mailing list, web interface at