* Erik Lax [2012-01-31 16:51]:
> I noticed that tcpbench tries to setpgid() for no obvious reason (to
> me) since it's not forked anymore. Previously, 2 years ago it was
> fork()ed and utilized killpg() etc. Could this be a leftover? I'm
> running into issues spawning tcpbench since my parent proc
On 31 January 2012 13:50, Erik Lax wrote:
> Hi,
>
> I noticed that tcpbench tries to setpgid() for no obvious reason (to me)
> since it's not forked anymore. Previously, 2 years ago it was fork()ed and
> utilized killpg() etc. Could this be a leftover? I'm running into issues
> spawning tcpbench s
On 31 January 2012 13:50, Erik Lax wrote:
> Hi,
>
> I noticed that tcpbench tries to setpgid() for no obvious reason (to me)
> since it's not forked anymore. Previously, 2 years ago it was fork()ed and
> utilized killpg() etc. Could this be a leftover? I'm running into issues
> spawning tcpbench s
Hi,
I noticed that tcpbench tries to setpgid() for no obvious reason (to me)
since it's not forked anymore. Previously, 2 years ago it was fork()ed
and utilized killpg() etc. Could this be a leftover? I'm running into
issues spawning tcpbench since my parent process uses setsid().
I attached
