Date: Wed, 12 Apr 2017 02:00:31 +0200 From: Jan Beich <jbeich@FreeBSD.org> To: Christoph Moench-Tegeder <cmt@burggraben.net> Cc: freebsd-gecko@freebsd.org, freebsd-threads@freebsd.org Subject: Re: FreeBSD Port: www/firefox Message-ID: <o9w2-ebq8-wny@FreeBSD.org> References: <CAFn_OkF1V3CHTQCQFG_HDJ5dmuXvTYxX6UOoe81rpKyiF19WcA@mail.gmail.com> <1491928081558-6179754.post@n6.nabble.com> <37de-onxw-wny@FreeBSD.org> <20170411182519.GB1556@elch.exwg.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Christoph Moench-Tegeder <cmt@burggraben.net> writes: > ## Jan Beich (jbeich@FreeBSD.org): > >> Walter Schwarzenfeld (privately) writes: >> > With gtk3 on it starts after sysctl p1003_1b.sem_nsems_max=512. >> > Please => pkg-message. >> >> Don't use sem(4), it's deprecated since FreeBSD 9.0. p1003_1b.sem_nsems_max >> doesn't have an effect with the new implementation. >> >> https://svnweb.freebsd.org/changeset/base/201546 > > Um. Firefox' "configure" code explicitly checks the maximum number > of semaphores via sysconf(_SC_SEM_NSEMS_MAX) (that's in > python/futures/concurrent/futures/process.py l. 250). As far as I > can tell, in FreeBSD 10.3 that value is set by sysctl > p1003_1b.sem_nsems_max - so at least for the "old" FreeBSD, that > would be the way to go? (and it worked for me). FreeBSD 8.x has been EOL since 2015-08-01. However, sysconf() ends up using sem(4) even for new code. Maybe someone from threads@ knows more. $ getconf SEM_NSEMS_MAX undefined $ kldload sem $ getconf SEM_NSEMS_MAX 30 > Further, the sem(4) manpage has no deprecation note...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?o9w2-ebq8-wny>