(Otherwise `prove` would complain about “out of sequence” tests.)

* n-times-fadvise:
  Update man pages to reflect "-n" option
  Only do multi-fadvise if previous call was successful
  Add explanation of -n flag / NOCACHE_NR_FADVISE env variable
  Implement "-n <n>" flag for repeated posix_fadvise()

There was a trivial-to-solve merge conflict in nocache.c

Reported-by: Reda Noushi <reda@logzilla.pro>

> one remark: what should nocache do if a non-zero value is returned by posix_fadvise()?
> 1. is it okay to continue executing it and returning the last value?
> 2. or stop execution and return the last non-zero value of fadv()?

* noushi/behavior_mods:
  nocache retrieves max fds from actual process limits.

* 'master' of git://github.com/paulharris/nocache:
  Adjusted script so it will preload the .so from the script's directory

Thanks again, kocmo, for noticing.

Thanks to kocmo for the patch.

man pages

* test:
  Add "ls" test
  Make it easy to add new tests
  Add make target “test”
  Add very basic test

This issue came up in the real world because apparently
libselinux.so.1 does an fopen in a constructor function.
Big Thanks to Mike Shal (http://sourceware.org/ml/libc-help/2009-06/msg00000.html )

[Made some cosmetic changes -JP]

Fixes: GitHub issues #1 and #2
Signed-off-by: Julius Plenz <julius@plenz.com>

Calls to open() from within glibc cannot be intercepted
(see <http://cygwin.com/ml/libc-alpha/2006-04/msg00094.html>);
thus, include wrappers for fopen() and fclose() as well.

This should possibly be done for fdopen() and freopen(),
too, if there's need for it.

[Patch corrected and original description translated by Julius Plenz]
Signed-off-by: Julius Plenz <plenz@cis.fu-berlin.de>

When you invoke "tar cfv <tarball> <files>", then tar will close all
active file descriptors it has, forks, then opens the target tarball
as fd 1 (stdout). Then, it'll exec "gzip -", which *inherits* a stdout
which is a file.

Now we duplicate this stdout if it's a regular file so that we can
advise it later. (The original will be closed via the _exit() routine,
probably, which uses direct syscall that we cannot intercept.)

Thus, also shell redirection -- which makes heavy use of dup2() --  is handled
correctly:

    $ cachestats /tmp/foo
    open: No such file or directory
    $ nocache sh -c 'echo foo > /tmp/foo'
    $ cachestats /tmp/foo
    pages in cache: 0/1 (0.0%)  [filesize=0.0K, pagesize=4K]

* tar-quirks:
  Add an alias __openat_2() for openat()
  intercept creat()

Don't ask me for the reason why a straight-forward openat() call in
GNU tar ends up calling __openat_2() via the glibc. I don't know.
Anyway, that's the first time I had to ask something on StackOverflow,
and I was promptly pointed in the right direction!
<http://stackoverflow.com/questions/9161116/intercepting-the-openat-system-call-for-gnu-tar>