It's funny because one of my coworkers had exactly the same problem last week.
It fails because under the hood, the backtick operator calls fork and the OS following a conservative approach, aborts the operation because it doesn't have enough memory to hold two process images that big.
The simplest workaround is to allow the kernel to do memory overcommit.
Or alternatively, you could increase the swap space on the machine.
Update:
For perl porters reading this: wouldn't it be possible to use vfork() where supported by the OS to implement qx, system or open(... | ...), etc.?
At some point in the past any decent OS got COW making vfork mostly useless, but now, machines without or with very tiny swap spaces are becoming common making vfork pertinent again!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.