Mailing List Archive: Linux: Kernel

process groups and session ids.

Index | Next | Previous | View Threaded

astor at guardian

Mar 16, 1998, 6:32 AM

Post #1 of 3 (24 views)
Permalink

process groups and session ids.

Can a process have a process group or a session id that doesn't
correspond to an existing process? I'm adding random pids and need to
know whether I can just check the pidhashtable or if I need to go
through the tasklist as well.
astor
--
Alexander Kjeldaas, Guardian Networks AS, Trondheim, Norway
http://www.guardian.no/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger

schwab at issan

Mar 18, 1998, 4:00 AM

Post #2 of 3 (22 views)
Permalink

Re: process groups and session ids. [In reply to]

Alexander Kjeldaas <astor [at] guardian> writes:
|> Can a process have a process group or a session id that doesn't
|> correspond to an existing process?
Yes, the session or process group leader may have died already. For
example, you can put a process in the background and then log out, or the
process group leader could have been the head of a pipe, but the consumer
didn't finish yet processing the input even after it received EOF from the
pipe.
--
Andreas Schwab "And now for something
schwab [at] issan completely different"
schwab [at] gnu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger

astor at guardian

Mar 18, 1998, 4:22 AM

Post #3 of 3 (22 views)
Permalink

Re: process groups and session ids. [In reply to]

On Wed, Mar 18, 1998 at 12:00:56PM +0100, Andreas Schwab wrote:
> Alexander Kjeldaas <astor [at] guardian> writes:
>
> |> Can a process have a process group or a session id that doesn't
> |> correspond to an existing process?
>
> Yes, the session or process group leader may have died already. For
> example, you can put a process in the background and then log out, or the
> process group leader could have been the head of a pipe, but the consumer
> didn't finish yet processing the input even after it received EOF from the
> pipe.
>
That's what I thought too. I'm therefore designing a feature that will
get this information fast. [.And in the process remove most unneeded
for_each_tasks in the kernel (fork,exit,setsig etc)].
astor
--
Alexander Kjeldaas, Guardian Networks AS, Trondheim, Norway
http://www.guardian.no/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads