On 2001.08.07, Jim Wilcoxson <[EMAIL PROTECTED]> wrote:
> Under 2.3.3, if a scheduled proc did a [ns_thread getid], it got back
> a number that corresponded to a Linux process (on Linux, every thread
> is a separate process). That isn't the case with 3.4 for scheduled
> procs. I don't know what the number is/means.
Is every thread a process, or does Linux just implement threads
using a process pool (where each process is responsible for N-number
of threads, where N=1 could be true).
Perhaps in 3.4 things were changed to allow each process to handle
>1 thread. So, now the thread ID doesn't map onto the process ID.
I'm _just guessing_ here.
> The AD version has a special SEGV sig handler to kill the main process
> if compiled under Linux. This isn't in the 3.4 version. The "hanging
> around" behavior under Linux means that init won't restart the server
> if it segv's. Lots of hassles because of this.
Hmm. Since I went to 3.4, I haven't seen the hanging around behavior
anymore, either, and I'm using the vanilla 3.4 as it is in SourceForge
CVS. Interesting.
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
