Date: Thu, 30 Oct 2003 01:28:30 +0200 From: Alexey Zelkin <phantom@FreeBSD.org.ua> To: Dan Nelson <dnelson@allantgroup.com> Cc: java@freebsd.org Subject: Re: [phantom@FreeBSD.org: cvs commit: ports/java/jdk14 Makefile pkg-plist ports/java/jdk14/files patch-UNIXProcess_md.c.bsd] Message-ID: <20031030012830.A37865@phantom.cris.net> In-Reply-To: <20031029193106.GA95197@dan.emsphone.com>; from dnelson@allantgroup.com on Wed, Oct 29, 2003 at 01:31:06PM -0600 References: <20031029103341.A32272@phantom.cris.net> <20031029193106.GA95197@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
hi, On Wed, Oct 29, 2003 at 01:31:06PM -0600, Dan Nelson wrote: > In the last episode (Oct 29), Alexey Zelkin said: > > phantom 2003/10/29 00:20:59 PST > > > > FreeBSD ports repository > > > > Modified files: > > java/jdk14 Makefile pkg-plist > > Added files: > > java/jdk14/files patch-UNIXProcess_md.c.bsd > > Log: > > . Add fix for "runaway process" problem. It should fix of stalled > > processes problem for people who use Runtime.getRuntime.exec() method > > and related things. Least five people reported that this patch fixed > > problem for them. > > > > IMPORTANT: I'd also suggested to all jdk14 users who runs FreeBSD 4.x > > and use libc_r at FreeBSD 5.x to upgrade. > > jhb just committed a patch to -current that fixes a bug where a SIGPROF > timer (i.e. libc_r's thread scheduling signal) would continue to fire > in the client process after a fork. You might want to check and see if > you can reproduce your bug with a new -current. Your patch will still > be needed for 4.9, of course. I am aware of this patch. But it can affect "critical section" requirement only, i.e. with this patch I don't need to suspend/resume threads while calling to __SYS_fork(). But I'll not do even it because we can't expect everyone who want to run jdk will upgrade to most recent -CURRENT.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031030012830.A37865>