--- IO-AIO/AIO.pm	2017/06/23 22:33:06	1.273
+++ IO-AIO/AIO.pm	2017/09/22 12:17:49	1.277
@@ -279,6 +279,7 @@
    IO::AIO::nreqs
    IO::AIO::nready
    IO::AIO::npending
+   IO::AIO::min_fdlimit $nfd;
 
    IO::AIO::sendfile $ofh, $ifh, $offset, $count
    IO::AIO::fadvise $fh, $offset, $len, $advice
@@ -960,6 +961,8 @@
 destination) from C<$srcpath> to C<$dstpath> and call the callback with
 a status of C<0> (ok) or C<-1> (error, see C<$!>).
 
+Existing destination files will be truncated.
+
 This is a composite request that creates the destination file with
 mode 0200 and copies the contents of the source file into it using
 C<aio_sendfile>, followed by restoring atime, mtime, access mode and
@@ -1078,7 +1081,7 @@
 names, directories you can recurse into (directories), and ones you cannot
 recurse into (everything else, including symlinks to directories).
 
-C<aio_scandir> is a composite request that creates of many sub requests_
+C<aio_scandir> is a composite request that generates many sub requests.
 C<$maxreq> specifies the maximum number of outstanding aio requests that
 this function generates. If it is C<< <= 0 >>, then a suitable default
 will be chosen (currently 4).
@@ -1607,8 +1610,8 @@
 nowhere at all), while the directory fd, if available on the system,
 will still point to the original directory. Most functions accepting a
 pathname will use the directory fd on newer systems, and the string on
-older systems. Some functions (such as realpath) will always rely on the
-string form of the pathname.
+older systems. Some functions (such as C<aio_realpath>) will always rely on
+the string form of the pathname.
 
 So this functionality is mainly useful to get some protection against
 C<chdir>, to easily get an absolute path out of a relative path for future
@@ -2010,7 +2013,7 @@
 use an C<aio_group> together with a feed callback.
 
 Its main use is in scripts without an event loop - when you want to stat
-a lot of files, you can write somehting like this:
+a lot of files, you can write something like this:
 
    IO::AIO::max_outstanding 32;
 
@@ -2066,6 +2069,27 @@
 
 =over 4
 
+=item $numfd = IO::AIO::get_fdlimit
+
+Tries to find the current file descriptor limit and returns it, or
+C<undef> and sets C<$!> in case of an error. The limit is one larger than
+the highest valid file descriptor number.
+
+=item IO::AIO::min_fdlimit [$numfd]
+
+Try to increase the current file descriptor limit(s) to at least C<$numfd>
+by changing the soft or hard file descriptor resource limit. If C<$numfd>
+is missing, it will try to set a very high limit, although this is not
+recommended when you know the actual minimum that you require.
+
+If the limit cannot be raised enough, the function makes a best-effort
+attempt to increase the limit as much as possible, using various
+tricks, while still failing. You can query the resulting limit using
+C<IO::AIO::get_fdlimit>.
+
+If an error occurs, returns C<undef> and sets C<$!>, otherwise returns
+true.
+
 =item IO::AIO::sendfile $ofh, $ifh, $offset, $count
 
 Calls the C<eio_sendfile_sync> function, which is like C<aio_sendfile>,