Re: BUG: NTPL: waitpid() doesn't return?
From: bert hubert (ahu_at_ds9a.nl)
Date: 01/31/04
- Previous message: Greg KH: "Re: [PATCH] i2c driver fixes for 2.6.1"
- In reply to: Matthias Urlichs: "BUG: NTPL: waitpid() doesn't return?"
- Next in thread: Matthias Urlichs: "Re: BUG: NTPL: waitpid() doesn't return?"
- Reply: Matthias Urlichs: "Re: BUG: NTPL: waitpid() doesn't return?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 31 Jan 2004 16:37:43 +0100 To: Matthias Urlichs <smurf@smurf.noris.de>
On Sat, Jan 31, 2004 at 11:46:06AM +0100, Matthias Urlichs wrote:
> This partial trace is from Debian's mini-dinstall, which is a
> multithreaded Python script.
>
> What happens here is that it spawns a bunch of threads, then some of
> these fork+execve external programs which they waitpid() for.
>
> Unfortunately, some of these waitpid() calls don't return even though
> the waited-for process clearly has exited.
It might be that in the NPTL world only one waitpid() can run per process
simultaneously? Do you wait for all pids or for a specific one?
Bert.
-- http://www.PowerDNS.com Open source, database driven DNS Software http://lartc.org Linux Advanced Routing & Traffic Control HOWTO - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Greg KH: "Re: [PATCH] i2c driver fixes for 2.6.1"
- In reply to: Matthias Urlichs: "BUG: NTPL: waitpid() doesn't return?"
- Next in thread: Matthias Urlichs: "Re: BUG: NTPL: waitpid() doesn't return?"
- Reply: Matthias Urlichs: "Re: BUG: NTPL: waitpid() doesn't return?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|