This is the mail archive of the frysk@sources.redhat.com mailing list for the frysk project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: adding a second notify to the fork and clone observers

From: Andrew Cagney <cagney at redhat dot com>
To: pmuldoon at redhat dot com, Sami Wagiaalla <swagiaal at redhat dot com>
Cc: frysk <frysk at sources dot redhat dot com>
Date: Wed, 19 Apr 2006 15:45:32 -0400
Subject: Re: adding a second notify to the fork and clone observers
References: <4437F0F4.2020804@redhat.com> <1144694988.6095.19.camel@localhost.localdomain> <443AC037.2060804@redhat.com>

Picking up on the follow fork/clone problem again - an easy way to follow offspring.

There might be another solution: just have the core propagate Attached observers to any thread's offspring. Doing that would make the mechanism independant of the fork/exec observers. With that mechanism, everytime a new offspring is created, there would be an updateAttached notification.

thoughts?

Andrew

Follow-Ups:
- Re: adding a second notify to the fork and clone observers
  - From: Sami Wagiaalla

References:
- adding a second notify to the fork and clone observers
  - From: Andrew Cagney
- Re: adding a second notify to the fork and clone observers
  - From: Phil Muldoon
- Re: adding a second notify to the fork and clone observers
  - From: Andrew Cagney

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]