09-20-2013
Quote:
Originally Posted by
Rahulne25
Thanks, its working fine in RHEL,but i am getting an error in solaris10 server when i execute that script....
Simply saying "an error" is absolutely useless feedback. At the very least, copy/paste any error messages. If there are none, then describe the error in detail.
I suspect the error is caused by not having stat or having a stat implementation that implements a different command line option syntax.
Regards,
Alister
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am working on HP-Unix.
I have a 600 MB file in compressed form.
During decompression, when file size reaches
2GB, decompression aborts.
What should be done? (3 Replies)
Discussion started by: Nadeem Mistry
3 Replies
2. Programming
My C++ program returns 'Disk Full' Message when I tried to manage a file larger than 2Gb. the process is very simple: based on a TXT file, the process combine the information generating another temporary file (generating the error) to fillup a database.
My FS, during the process, reaches 40%...... (4 Replies)
Discussion started by: ASOliveira
4 Replies
3. Shell Programming and Scripting
Can an expert kindly write an efficient Linux ksh script that will split a large 2 GB text file into two?
Here is a couple of sample record from that text file:
"field1","field2","field3",11,22,33,44
"TG","field2b","field3b",1,2,3,4
The above rows are delimited by commas.
This script is to... (2 Replies)
Discussion started by: ihot
2 Replies
4. UNIX for Dummies Questions & Answers
Hi experts,
How do i find which are the filesystems which has crossed 90% capacity in solaris box.
thanks
Shaan:) (4 Replies)
Discussion started by: shaan_dmp
4 Replies
5. UNIX for Dummies Questions & Answers
Hi All,
We are running HP rp7400 box with hpux 11iv1.
Recently, we changed 3 kernel parameters
a) msgseg from 32560 to 32767
b) msgmnb from 65536 to 65535
c) msgssz from 128 to 256
Then we noticed that all application debug file size increase upto 2GB then it stops. So far we did not... (1 Reply)
Discussion started by: mhbd
1 Replies
6. AIX
I am trying to execute a database dump to a file, but can't seem to get around the 2GB file size. I have tried setting the user limit to -1, but no luck. (4 Replies)
Discussion started by: markper
4 Replies
7. Programming
Hi,
I've created a simple application that is supposed to fill up a file with messages up
to the size I pass as parameter.
The problem is that once the file reaches the 2GB size, it stops growing.
The flow of the application, for what is worth, is as follows:
while ( bytes written <... (7 Replies)
Discussion started by: emitrax
7 Replies
8. Linux
I am not able to unzip file greater then 2gb,
Any suggestions how to do that in linux?
Regards,
Manoj (5 Replies)
Discussion started by: manoj.solaris
5 Replies
9. UNIX for Advanced & Expert Users
Hi,
I am executing a SQL query and the output is more than 2GB. Hence the process is failing. How can I have a file created more than 2GB ?
Thanks,
Risshanth (1 Reply)
Discussion started by: risshanth
1 Replies
10. HP-UX
Greetings,
I'm attempting to dump a filesystem from a RHEL5 Linux server to a VXFS filesystem on an HP-UX server. The VXFS filesystem is large file enabled and I've confirmed that I can copy/scp a file >2GB to the filesystem.
# fsadm -F vxfs /os_dumps
largefiles
# mkfs -F vxfs -m... (12 Replies)
Discussion started by: bkimura
12 Replies
LEARN ABOUT LINUX
fstatat
FSTATAT(2) Linux Programmer's Manual FSTATAT(2)
NAME
fstatat - get file status relative to a directory file descriptor
SYNOPSIS
#include <fcntl.h> /* Definition of AT_* constants */
#include <sys/stat.h>
int fstatat(int dirfd, const char *pathname, struct stat *buf,
int flags);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
fstatat():
Since glibc 2.10:
_XOPEN_SOURCE >= 700 || _POSIX_C_SOURCE >= 200809L
Before glibc 2.10:
_ATFILE_SOURCE
DESCRIPTION
The fstatat() system call operates in exactly the same way as stat(2), except for the differences described in this manual page.
If the pathname given in pathname is relative, then it is interpreted relative to the directory referred to by the file descriptor dirfd
(rather than relative to the current working directory of the calling process, as is done by stat(2) for a relative pathname).
If pathname is relative and dirfd is the special value AT_FDCWD, then pathname is interpreted relative to the current working directory of
the calling process (like stat(2)).
If pathname is absolute, then dirfd is ignored.
flags can either be 0, or include the following flag:
AT_SYMLINK_NOFOLLOW
If pathname is a symbolic link, do not dereference it: instead return information about the link itself, like lstat(2). (By
default, fstatat() dereferences symbolic links, like stat(2).)
RETURN VALUE
On success, fstatat() returns 0. On error, -1 is returned and errno is set to indicate the error.
ERRORS
The same errors that occur for stat(2) can also occur for fstatat(). The following additional errors can occur for fstatat():
EBADF dirfd is not a valid file descriptor.
EINVAL Invalid flag specified in flags.
ENOTDIR
pathname is relative and dirfd is a file descriptor referring to a file other than a directory.
VERSIONS
fstatat() was added to Linux in kernel 2.6.16.
CONFORMING TO
POSIX.1-2008. A similar system call exists on Solaris.
NOTES
See openat(2) for an explanation of the need for fstatat().
SEE ALSO
openat(2), stat(2), path_resolution(7), symlink(7)
COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2009-12-13 FSTATAT(2)