07-18-2003
Actually, a command like "fsadm /dev/vg00/rlvol1" should be used to see if largefile support is enabled. Note that the mount option will only "attempt" to allow large files.
setrlimit() and ulimit() can be used to limit the size of file that a program can create.
HP-UX supports two ways for a 32 bit program to use large files. If you define _FILE_OFFSET_BITS to be 64 at compile time, the regular system calls now handle large files. If you define _LARGEFILE64_SOURCE a bunch of routines like open64() become available. I have never used either. I just compile in 64 bit mode which is done by using +DD64 on the cc comand line. But there is a "long long" datatype which is a 64 bit integer in either 32 bit or 64 bit mode.
Also see
this.
Last edited by Perderabo; 07-31-2005 at 10:54 AM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We have two files /var/adm/wtmp and /var/opt/OV/tmp/OpC/guiagtdf
Could you please tell me if what these files are and if I can purge them as they are very big and Vi will not let me look at them, it gives me a message 'file to long'.
Help any ideas
Thanks
:cool: (3 Replies)
Discussion started by: A Roberts
3 Replies
2. Shell Programming and Scripting
hi ,
iam trying to sort millions of records which is delimited and i cant able to
use sort command more than 60 million..if i try to do so i got an message stating that "File size limit exceeded",Is there any file size limit for using sort command..
How can i solve this problem.
thanks
... (7 Replies)
Discussion started by: cskumar
7 Replies
3. Filesystems, Disks and Memory
Hi,
when can a unix library file size become zero? For example.: can mistyping this command -> /usr/ucb/ps -auxww|grep -i <process name> make the "ps" library file size to become zero or its contents to get deleted? Is there any other way that an inadvertant mistake could cause the file size to... (1 Reply)
Discussion started by: ananthmm
1 Replies
4. UNIX for Dummies Questions & Answers
I have a file on solaris/linux.
ls -ls shows the logical size to be: 13292
However, when I transfer the file to my windows machine.. Rightclick->Properties shows the file size as: 13421
I wrote a small program on unix and windows that does a stat() on the file and reports the st_size... (6 Replies)
Discussion started by: the_learner
6 Replies
5. UNIX for Dummies Questions & Answers
What's the maximum file size supported by unix. (3 Replies)
Discussion started by: nagalenoj
3 Replies
6. Shell Programming and Scripting
I want to find the size of particular file exists in a particular directory
and i wnt to zip it.
In the below mentioned code it should check the MQ.log in the
particular directory.Please correct my code so that it will check
for particular MQ.log but i could not able to check whether
the... (9 Replies)
Discussion started by: Balachandar
9 Replies
7. UNIX for Advanced & Expert Users
Anybody can help
HOW TO FIND THE FILE SIZE IN UNIX (5 Replies)
Discussion started by: lmraochodisetti
5 Replies
8. Shell Programming and Scripting
Hi,
I have a file by redirecting some contents in unix shell.
Even when there is no content that is being redirected, the file size still shows greater than zero.
but even if there is no matching pattern the file APPRES has size greater than 0bytes.
awk -f AA.awk $logfile>APPRES... (3 Replies)
Discussion started by: justchill
3 Replies
9. Shell Programming and Scripting
to get the most granular size of a file, you can do so with:
solaris hosts:
ls -l /tmp/filea | awk '{print $4}'
linux hosts:
ls -l /tmp/filea | awk '{print $5}'
Is there a more universal command that will give the file size?
i'm leery of this ls command because the fields in... (21 Replies)
Discussion started by: SkySmart
21 Replies
10. UNIX for Beginners Questions & Answers
Hi All,
I am trying to sftp, get a file from remote server.
Post this we need to check the remote server file size or checksum value of the remote server file and compare it with the file size in the current server.
But I am facing issue to get the remote server file size. Could you please... (2 Replies)
Discussion started by: abhi_123
2 Replies
LEARN ABOUT SUNOS
lfcompile64
lfcompile64(5) Standards, Environments, and Macros lfcompile64(5)
NAME
lfcompile64 - transitional compilation environment
DESCRIPTION
All 64-bit applications can manipulate large files by default. The transitional interfaces described on this page can be used by 32-bit and
64-bit applications to manipulate large files.
In the transitional compilation environment, explicit 64-bit functions, structures, and types are added to the API. Compiling in this
environment allows both 32-bit and 64-bit applications to access files whose size is greater than or equal to 2 Gbyte ( 2**31 bytes).
The transitional compilation environment exports all the explicit 64-bit functions (xxx64()) and types in addition to all the regular func-
tions (xxx()) and types. Both xxx() and xxx64() functions are available to the program source. A 32-bit application must use the xxx64()
functions in order to access large files. See the lf64(5) manual page for a complete listing of the 64-bit transitional interfaces.
The transitional compilation environment differs from the large file compilation environment, wherein the underlying interfaces are bound
to 64-bit functions, structures, and types. An application compiled in the large file compilation environment is able to use the xxx()
source interfaces to access both large and small files, rather than having to explicitly utilize the transitional xxx64() interface calls
to access large files. See the lfcompile(5) manual page for more information regarding the large file compilation environment.
Applications may combine objects produced in the large file compilation environment with objects produced in the transitional compilation
environment, but must be careful with respect to interoperability between those objects. Applications should not declare global variables
of types whose sizes change between compilation environments.
For applications that do not wish to conform to the POSIX or X/Open specifications, the 64-bit transitional interfaces are available by
default. No compile-time flags need to be set.
Access to Additional Large File Interfaces
Applications that wish to access the transitional interfaces as well as the POSIX or X/Open specification-conforming interfaces should use
the following compilation methods and set whichever feature test macros are appropriate to obtain the desired environment (see stan-
dards(5)).
o Set the compile-time flag _LARGEFILE64_SOURCE to 1 before including any headers.
o Use the getconf(1) command with one or more of the following arguments:
+------------------+----------------------------------------+
| argument | purpose |
|LFS64_CFLAGS | obtain compilation flags necessary to |
| | enable the transitional compilation |
| | environment |
|LFS64_LDFLAGS | obtain link editor options |
|LFS64_LIBS | obtain link library names |
|LFS64_LINTFLAGS | obtain lint options |
+------------------+----------------------------------------+
EXAMPLES
In the following examples, the transitional compilation environment is accessed by invoking the getconf utility with one of the arguments
listed in the table above. The additional large file interfaces are accessed either by specifying -D_LARGEFILE64_SOURCE or by invoking the
getconf utility with the arguments listed above.
The example that uses the form of command substitution specifying the command within parentheses preceded by a dollar sign can be executed
only in a POSIX-conforming shell such as the Korn Shell (see ksh(1)). In a shell that is not POSIX-conforming, such as the Bourne Shell
(see sh(1)) and the C Shell (see csh(1)), the command must be enclosed within grave accent marks.
Example 1: An example of compiling a program using transitional interfaces such as lseek64() and fopen64():
$ c89 -D_LARGEFILE64_SOURCE
$(getconf LFS64_CFLAGS) a.c
$(getconf LFS64_LDFLAGS)
$(getconf LFS64_LIBS)
Example 2: An example of running lint on a program using transitional interfaces:
% lint -D_LARGEFILE64_SOURCE
`getconf LFS64_LINTFLAGS` ...
`getconf LFS64_LIBS`
SEE ALSO
getconf(1), lseek(2), fopen(3C), lf64(5), standards(5)
SunOS 5.10 26 Jan 1998 lfcompile64(5)