Re: Py2.7/FreeBSD: maximum number of open files

Date	2011-11-14 18:13 +0100
From	Christian Heimes <lists@cheimes.de>
Subject	Re: Py2.7/FreeBSD: maximum number of open files
References	<634914A010D0B943A035D226786325D42D0C264772@EXVMBX020-12.exch020.serverdata.net> <j9rfda$mfs$1@dough.gmane.org> <634914A010D0B943A035D226786325D42D0C2647C8@EXVMBX020-12.exch020.serverdata.net> <4EC1470B.90403@cheimes.de> <634914A010D0B943A035D226786325D42D0C2647EB@EXVMBX020-12.exch020.serverdata.net>
Newsgroups	comp.lang.python
Message-ID	<mailman.2706.1321290793.27778.python-list@python.org> (permalink)

Show all headers | View raw

Am 14.11.2011 18:03, schrieb Tobias Oberstein:
> This is unbelievable.
> 
> I've just tested: the bug (in libc) is still there on FreeBSD 8.2 p3 ... both on i386
> _and_ amd64.
> 
> Now I'm f***d;(
> 
> A last chance: is it possible to compile Python for not using libc fopen(),
> but the Posix open()?
> 
> Thanks anyway for this hint!

A fix would break the ABI compatibility. I guess that you won't see a
fix for the issue until FreeBSD 9.0 is released.

And no, you can't re-compile Python to use the open() API instead of
fopen(). The built-in file type is developed around the file pointer
API, not the file descriptor API. Luckily Python 2.7 has a backport of
Python 3.x new IO library. The new IO API doesn't use file pointers at
all and implements its own layer around file descriptors. Good luck!

Christian

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Py2.7/FreeBSD: maximum number of open files Christian Heimes <lists@cheimes.de> - 2011-11-14 18:13 +0100

csiph-web