Wow. That link makes Sun look pretty bad.
Notice however, that it's not an OS limitation, but a (32-bit) C runtime library one.
From your link:
The following discussion is relevant only in 32-bit applications, as 64-bit applications are immune to the limitation to 256 file descriptors.
An obvious way to work around this limitation therefore is to use a 64-bit Perl. Or to build your own Perl. What version of Perl are you currently using? Who built it? It would help if you could run "perl -V" and post its output here.
Update: For cheap thrills, I just did a little experiment and built perl 5.12.1 with default settings as a 32-bit executable with both the Solaris C compiler and with gcc. The Solaris compiler built perl suffered from the dreaded 256 file descriptor limit, while the gcc compiler built perl did not. This is as I expected because gcc uses the glibc C runtime library (RTL) and so does not suffer from the (appalling) Solaris C RTL 256 file descriptor limit. So, in addition to downloading or building a SPARC 64-bit perl (ActiveState and others should provide these for download) you could download or build a SPARC 32-bit gcc-built perl.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
