From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Tanaka Akira <akr@m17n.org>, zsh-workers@sunsite.auc.dk
Subject: Re: fg/bg on FreeBSD.
Date: Sat, 6 May 2000 21:23:52 +0000 [thread overview]
Message-ID: <1000506212352.ZM8935@candle.brasslantern.com> (raw)
In-Reply-To: <hvou2gbmow8.fsf@serein.m17n.org>
On May 7, 4:58am, Tanaka Akira wrote:
} Subject: Re: fg/bg on FreeBSD.
}
} In article <hvozoq3mux1.fsf@serein.m17n.org>,
} Tanaka Akira <akr@m17n.org> writes:
}
} > Possibly. But NetBSD has no problem...
}
} I found the difference between FreeBSD and NetBSD.
}
} FreeBSD fails to kill(-PGID,0) for zombie process but NetBSD (and
} Linux) succeeds.
}
[...]
}
} I confirmed following modification prevents the problem. But
} definitely this is too radical...
}
} Index: Src/exec.c
} ===================================================================
} - if (killpg(jobtab[list_pipe_job].gleader, 0) == -1 ||
} + if (/* killpg(jobtab[list_pipe_job].gleader, 0) == -1 || */
} setpgrp(0L, jobtab[list_pipe_job].gleader) == -1) {
What happens if you reverse the order of the test?
if (setpgrp(0L, jobtab[list_pipe_job].gleader) == -1 ||
killpg(jobtab[list_pipe_job].gleader, 0) == -1) {
What I'm trying to discover is whether killpg() continues to fail after
a process is successfully added to the group.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-05-06 21:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-06 15:03 Tanaka Akira
2000-05-06 17:08 ` Bart Schaefer
2000-05-06 17:48 ` Tanaka Akira
2000-05-06 18:45 ` Bart Schaefer
2000-05-06 19:03 ` Tanaka Akira
2000-05-06 19:58 ` Tanaka Akira
2000-05-06 21:23 ` Bart Schaefer [this message]
2000-05-06 21:41 ` Tanaka Akira
2000-05-08 8:48 Sven Wischnowsky
2000-05-08 9:17 ` Tanaka Akira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1000506212352.ZM8935@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=akr@m17n.org \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).