10-06-2005
Ah OK, you need to use interfaces
in your program that allow you to have
files > 2GB.
For linux (glibc) you can do it explicitly
in the source by defining _LARGEFILE64_SOURCE
and then calling open(,O_LARGEFILE), stat64() etc.
You can also get everything working implicitly
in 64 bit mode by just defining _FILE_OFFSET_BITS=64
10 More Discussions You Might Find Interesting
1. Solaris
Does anyone know how to get around the unix group file limitation whereby you have a limit of 1024 characters when adding users to a unix group? (3 Replies)
Discussion started by: asmillie
3 Replies
2. HP-UX
Hi All,
Can anyone please clarify me the following questions:
1. Is there any file size limitation in HP-UX 11i, that I can able to create upto certain size of file (say 2 GB) and not more then that????
2. At max. how many files we can able to keep inside a folder????
3. How many... (2 Replies)
Discussion started by: sundeep_mohanty
2 Replies
3. Linux
Hi
I am trying to rcp a file from Solaris box to Linux.
When the file size is 2,205,255,047, the rcp fails with the message
Jan 10 01:11:53 hqsas167 rsh: pam_authenticate: error Authentication failed
However when I rcp a file with smaller size - 9,434,477 - the rcp completes with... (2 Replies)
Discussion started by: schoubal
2 Replies
4. UNIX for Dummies Questions & Answers
Dear all
Recently I cant touch file in one mount point (which is not full, 78% full only), it says can't write to device, obviously it means it's full, I deleted some files and I can write some files only. I wonder is there any file number limitation in a mount point and how can I check or how... (2 Replies)
Discussion started by: shanemcmahon
2 Replies
5. Shell Programming and Scripting
Hi to every body there,
I am new this forum and this is my first post.
I am a new user of Unix,
is there any size limitation of files while creating tar file.
Thanks in advance (4 Replies)
Discussion started by: Manvar Khan
4 Replies
6. Shell Programming and Scripting
Hi,
I am using fetchmail in my application so as to download mails to the localhost where the application is hosted from the mailserver.Fetchmail is configured as as to run as a daemon polling mails during an interval of 1sec.
So my concern here is, during each 2sec it is writing two... (10 Replies)
Discussion started by: DILEEP410
10 Replies
7. UNIX for Advanced & Expert Users
Hi All,
I ran code in test environment to find the files more than 1TB given below is a snippet from code:
FILE_SYSTEM=/home/arun
MAX_FILE_LIMIT=1099511627776
find $FILE_SYSTEM -type f -size +"$MAX_FILE_LIMIT"c -ls -xdev 2>/dev/null |
while read fname
do
echo "File larger than... (3 Replies)
Discussion started by: Arunprasad
3 Replies
8. Solaris
Hello All,
I am using a SunOS machine. My application creates output files for the downstream systems. However output files are restricted to 2GB of file size in SunOS due to which I am forced to create multiple files which is not supported by the downstream due to some limitations.
Is... (5 Replies)
Discussion started by: pasupuleti81
5 Replies
9. Linux
Hi friends,
I tried to take a backup of my PC using tar command. But it ended with an error
tar: /home/backup/back.tar.gz: Cannot write: No space left on device
tar: Error is not recoverable: exiting now
But i checked the disk space and there is enough space is available.
]# df
Filesystem... (11 Replies)
Discussion started by: siva3492
11 Replies
10. Linux
Hello Friends,
I tried to take tar backup in my server, but it ended with an error.
It said that:
/home/back/pallava_backup/fbackup_backup/stape_config
/home/back/romam_new.tar.gz
tar: /home/backup/back.tar.gz: Cannot write: No space left on device
tar: Error is not recoverable: exiting... (10 Replies)
Discussion started by: siva3492
10 Replies
FSEEKO(3) Linux Programmer's Manual FSEEKO(3)
NAME
fseeko, ftello - seek to or report file position
SYNOPSIS
#include <stdio.h>
int fseeko(FILE *stream, off_t offset, int whence);
off_t ftello(FILE *stream);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
fseeko(), ftello():
_FILE_OFFSET_BITS == 64 || _POSIX_C_SOURCE >= 200112L
(defining the obsolete _LARGEFILE_SOURCE macro also works)
DESCRIPTION
The fseeko() and ftello() functions are identical to fseek(3) and ftell(3) (see fseek(3)), respectively, except that the offset argument of
fseeko() and the return value of ftello() is of type off_t instead of long.
On some architectures, both off_t and long are 32-bit types, but defining _FILE_OFFSET_BITS with the value 64 (before including any header
files) will turn off_t into a 64-bit type.
RETURN VALUE
On successful completion, fseeko() returns 0, while ftello() returns the current offset. Otherwise, -1 is returned and errno is set to
indicate the error.
ERRORS
See the ERRORS in fseek(3).
VERSIONS
These functions are available under glibc since version 2.1.
ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7).
+-------------------+---------------+---------+
|Interface | Attribute | Value |
+-------------------+---------------+---------+
|fseeko(), ftello() | Thread safety | MT-Safe |
+-------------------+---------------+---------+
CONFORMING TO
POSIX.1-2001, POSIX.1-2008, SUSv2.
SEE ALSO
fseek(3)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
2017-09-15 FSEEKO(3)