From owner-freebsd-current@FreeBSD.ORG Tue Jun 30 19:00:27 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62E2D1065680 for ; Tue, 30 Jun 2009 19:00:27 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id 1F0A98FC17 for ; Tue, 30 Jun 2009 19:00:26 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id 3B3671E001FA; Tue, 30 Jun 2009 21:00:26 +0200 (CEST) Received: from triton.kn-bremen.de (noident@localhost [127.0.0.1]) by triton.kn-bremen.de (8.14.3/8.14.3) with ESMTP id n5UIwut2041374; Tue, 30 Jun 2009 20:58:56 +0200 (CEST) (envelope-from nox@triton.kn-bremen.de) Received: (from nox@localhost) by triton.kn-bremen.de (8.14.3/8.14.3/Submit) id n5UIwuM0041373; Tue, 30 Jun 2009 20:58:56 +0200 (CEST) (envelope-from nox) From: Juergen Lock Date: Tue, 30 Jun 2009 20:58:56 +0200 To: Alexander Best Message-ID: <20090630185856.GA41198@triton.kn-bremen.de> References: <200906301828.n5UISAd0035828@triton.kn-bremen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-current@FreeBSD.org, Juergen Lock Subject: Re: nspluginwrapper patch for testing (was: Re: flash10 vs f10) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 19:00:27 -0000 On Tue, Jun 30, 2009 at 08:38:49PM +0200, Alexander Best wrote: > i'm running compat.linux.osrelease: 2.6.16 and r195173 (CURRENT). > > yep. the warning comes up if a users stacksize is limited < 32M. flash works > great and the HD button isn't causing any problems. > > maybe it's possible to ad something like > > if ulimit < 32m then don't change ulimit and prinf("not setting new ulimit due > to stacksize limitation"). > > something like that.... Well I just redirected the (possible) error message to /dev/null in the new version since the main point of this ulimit'ing is to get rid of a too high limit that can exhibit a flash bug. So If the limit is already lower that shouldn't cause a problem unless maybe when it is _very_ low indeed... Cheers, Juergen