[Rpm-devel] rpm-4.4.6 on solaris9-sparc64
fcusack at fcusack.com
Wed Jun 28 10:05:04 EDT 2006
On June 28, 2006 6:49:15 AM -0400 Jeff Johnson <n3npq.jbj at gmail.com> wrote:
> On Jun 28, 2006, at 1:11 AM, Frank Cusack wrote:
>> On June 26, 2006 4:04:18 PM -0400 Jeff Johnson
>> <n3npq.jbj at gmail.com> wrote:
>>> The historical issue that is forcing this horrendopusly
>>> complicated mess is that
>>> apiary (at one time the replacment for beehive) insisted on
>>> running rpmlib
>>> on a thread, and posix signals do not have SIGCHLD delivery to
>>> that thread.
>> Sorry for butting in, but why is rpm threaded?
> Note that any library can be put a thread, threaded or not, by loading a module in bindings on a
> rpmlib itself is not thread safe, but there are ways to run libraries on a single thread safely.
> However, SIGCHLD instantly ceases to be delivered to any signal handler on the thread thread.
How's that? Signal handlers are per-process, not per thread. If an
async signal (like SIGCHLD) is delivered, any thread not blocking it
might get it, but if there is a handler it probably doesn't matter
too much which thread takes it.
More information about the Rpm-devel