 |
» |
|
|
|
NAMEfgetpos64(), fopen64(), freopen64(), fseeko64(), fsetpos64(), fstatvfsdev64(), ftello64(), ftw64(), nftw64(), statvfsdev64(), tmpfile64() — non-POSIX standard API interfaces to support large files. SYNOPSIS#include <stdio.h> int fgetpos64(FILE *stream, fpos64_t *pos); #include <stdio.h> FILE *fopen64(const char *pathname, const char *type); #include <stdio.h> FILE *freopen64(const char *pathname, const char *type, FILE *stream); #include <stdio.h> int fseeko64(FILE *stream, off64_t *offset, int whence); #include <stdio.h> int fsetpos64(FILE *stream, const fpos64_t *pos); #include <sys/statvfs.h> int fstatvfsdev64(int filedes, struct statvfs64 *buf); #include <stdio.h> off64_t ftello64(FILE *stream); #include <ftw.h>
int ftw64(const char *path,
int (*fn)(const char *obj_path,
const struct stat64 *obj_stat,
int obj_flags),
int depth);
#include <ftw.h>
int nftw64(const char *path,
int (*fn)(const char *obj_path,
const struct stat64 *obj_stat,
int obj_flags,
struct FTW obj_FTW),
int depth,
int flags); #include <sys/statvfs.h> int statvfsdev64(const char *path, struct statvfs64 *buf); #include <stdio.h> FILE *tmpfile64(void); DESCRIPTIONNew API's to support large files. These API interfaces are not
a part of the POSIX standard and may be removed in the future.
- fgetpos64()
The
fgetpos64()
function is identical to
fgetpos()
except that
fgetpos64()
returns the position in a
fpos64_t
instead of a
fpos_t.
All other functional behaviors, returns, and errors are identical. - fopen64()
The
fopen64()
function is identical to
fopen()
in 64-bit compile environment. The
fopen64()
function returns a pointer to a FILE which can be used to grow the file past
2 GB if desired. All other functional behaviors, returns, and errors are
identical to
fopen(). - freopen64()
The
freopen64()
function is identical to
freopen()
in 64-bit compile environment. The
freopen64()
function returns a pointer to a FILE which can be used to grow the file past
2 GB if desired. All other functional behaviors, returns, and errors are
identical to
freopen(). - fseeko64()
The
fseeko64()
function is identical to
fseeko()
except that
fseeko64()
accepts an
off64_t
for the size parameter instead of
off_t.
All other functional behaviors, returns, and errors are identical. - fsetpos64()
The
fsetpos64()
function is identical to
fsetpos()
except that
fsetpos64()
accepts an
fpos64_t
for the pos parameter instead of
fpos_t.
All other functional behaviors, returns, and errors are identical. - fstatvfsdev64()
The
fstatvfsdev64()
function is identical to
fstatvfsdev()
except that
fstatvfsdev64()
accepts a
struct statvfs64
for the second parameter instead of
struct statvfs.
All other functional behaviors, returns, and errors are identical. - ftello64()
The
ftello64()
function is identical to
ftello()
except that
ftello64()
returns the file position in an
off64_t
instead of an
off_t.
All other functional behaviors, returns, and errors are identical. - ftw64()
The
ftw64()
function is identical to
ftw()
except that it that it utilizes a
struct stat64
as the second parameter to the function
whose pointer is passed to
ftw64().
All other functional behaviors, returns, and errors are identical. - nftw64()
The
nftw64()
function is identical to
nftw()
except that it that it utilizes a
struct stat64
as the second parameter to the function
whose pointer is passed to
nftw64().
All other functional behaviors, returns, and errors are identical. - statvfsdev64()
The
statvfsdev64()
function is identical to
statvfsdev()
except that
statvfsdev64()
accepts a
struct statvfs64
for the second parameter instead of
struct statvfs.
All other functional behaviors, returns, and errors are identical. - tmpfile64()
The
tmpfile64()
function is identical to
tmpfile()
in the 64-bit compile environment. Both interfaces
create a temporary file that is capable of growing
beyond 2GB's if desired. All other
functional behaviors, returns, and errors are identical.
APPLICATION USAGEfgetpos64(),
fopen64(),
freopen64(),
fseeko64(),
fsetpos64(),
fstatvfsdev64(),
ftello64(),
ftw64(),
nftw64(),
statvfsdev64(),
and
tmpfile64()
are thread-safe. These interfaces are not async-cancel-safe.
A cancellation point may occur when a thread is executing any of
these interfaces. |
