Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 Feb 2004 15:18:19 -0500 (EST)
From:      Daniel Eischen <eischen@vigrid.com>
To:        Hye-Shik Chang <perky@i18n.org>
Cc:        Kris Kennaway <kris@obsecurity.org>
Subject:   Re: python ports broken (sem_destroy: Resource temporarily unavailable)
Message-ID:  <Pine.GSO.4.10.10402061515230.6349-100000@pcnet5.pcnet.com>
In-Reply-To: <Pine.GSO.4.10.10402061426290.23540-100000@pcnet5.pcnet.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 6 Feb 2004, Daniel Eischen wrote:

> On Sat, 7 Feb 2004, Hye-Shik Chang wrote:
> > 
> > Thank you very much!
> > py-bsddb unittest is successfully passed with your fixes. And almost
> > all of python regression test set is okay except test_threaded_import.
> > 
> > alice(perky):/usr/local/lib/python2.3/test% sudo python test_threaded_import.py
> > Trying 20 threads ... OK.
> > Trying 50 threads ...
> > Traceback (most recent call last):
> >   File "test_threaded_import.py", line 56, in ?
> >     test_main()
> >   File "test_threaded_import.py", line 50, in test_main
> >     thread.start_new_thread(task, ())
> > thread.error: can't start new thread
> > 
> > FYI, python's thread creation routine is located on
> > work/Python-2.3.3/Python/thread_pthread.h:188.
> 
> How many threads does it try after "Trying 50 threads..."?  You
> may have to increase kern.threads.max_threads_per_proc.

Arghh.  It's creating system scope threads, so you have
to adjust kern.threads.max_groups_per_proc.

  $ sudo sysctl kern.threads.max_groups_per_proc=100
  kern.threads.max_groups_per_proc: 50 -> 100
  $ pwd
  /usr/local/lib/python2.3/test
  $ sudo python test_threaded_import.py
  Trying 20 threads ... OK.
  Trying 50 threads ... OK.
  Trying 20 threads ... OK.
  Trying 50 threads ... OK.
  Trying 20 threads ... OK.
  Trying 50 threads ... OK.

-- 
Dan Eischen



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10402061515230.6349-100000>