Your total free memory is obviously larger than 2GiB, but remember
that what's listed there is the total, while the offending usage
required a *contiguous* 2GiB region.
On Sat, Nov 1, 2014 at 7:56 PM, Bruce Dubbs bruce.du...@gmail.com wrote:
Jim Meyering wrote:
On Wed, Oct 29, 2014 at 2:56 PM,
Hello,
On 11/01/2014 10:39 PM, Paul Eggert wrote:
Assaf Gordon wrote:
$ ../../../src/grep -r '^' ; echo $?
a:a
b:b
../../../src/grep: c: Inappropriate file type or format
../../../src/grep: d: Inappropriate file type or format
../../../src/grep: e: Inappropriate file type or format
2
What
Jim Meyering wrote:
Your total free memory is obviously larger than 2GiB, but remember
that what's listed there is the total, while the offending usage
required a *contiguous* 2GiB region.
My understanding of the kernel is that it allocates in 4K blocks and
maps them to user space to appear
Assaf Gordon assafgor...@gmail.com wrote:
On 11/01/2014 10:39 PM, Paul Eggert wrote:
Assaf Gordon wrote:
$ ../../../src/grep -r '^' ; echo $?
a:a
b:b
../../../src/grep: c: Inappropriate file type or format
../../../src/grep: d: Inappropriate file type or format
../../../src/grep:
Norihiro Tanaka wrote:
/* Tru64 5.1B uses errno == ENOTSUP. */
Ah, I see that you were working on the same bug I was. I don't think we need to
worry about Tru64, partly because ENOTSUP would be troublesome anyway (does it
mean that O_NOFOLLOW isn't supported? if so, 'grep' has other
Norihiro Tanaka wrote:
/* Tru64 5.1B uses errno == ENOTSUP. */
Ah, I see that you were working on the same bug I was. I don't think
we need to worry about Tru64, partly because ENOTSUP would be troublesome
anyway (does it mean that O_NOFOLLOW isn't supported? if so, 'grep' has
other
