11-08-2010
Well, arrays seem to be inside languages, where you just reach out and touch them.
Perhaps you are asking about mmap()/mmap64(), which turn the file into a memory array so you never need to seek (and flush and reload buffers) ever again and you get the use of as much RAM as you can scrounge to hold most recently used pages, even if not currently mapped? JAVA has a similar facility, FileChannel. I suppose PERL can do this, perhpas calling mmap()/mmap64() directly. Solaris reads with mmap*() and it also is used in dynamic linking, so all users of a lib file have the same memory pages. If 40 people are running vi, why have 40 different copies in different VM/RAM locations?
Head and tail with character -c arguments do seek and read in the shell.
10 More Discussions You Might Find Interesting
1. Programming
sir,
i used lssek as this
lseek(fp,-10,2);
i am not getting any output i dont now why can you explan sir..
Thanks in advance,
Arunkumar (4 Replies)
Discussion started by: arunkumar_mca
4 Replies
2. Programming
Hi
My requirement is to convert the following to C++
char buffer;
sprintf(buffer,"%s %-50s %6s %-6d %s\n",a.substr(0,5),a.substr(10,20))
Since the buffer is of varying length, i cannot hardcode the value as 90.
i would like to convert the buffer to string object so that it can receive any... (1 Reply)
Discussion started by: dhanamurthy
1 Replies
3. Shell Programming and Scripting
I am using "ps ax" command in one of my scripts . AIX has x flag for ps . is there any equilent command for ps ax in solaris ?
Thanks (1 Reply)
Discussion started by: talashil
1 Replies
4. Programming
recently my project needs me to lseek a position over 4G size....
i found in linux or unix the parameters are all ulong 32 bits...the limit dooms the movement of a position over 4G
I was told that i should lseek64 to meet my need... but i have no idea where i can get the function neither by "man... (8 Replies)
Discussion started by: macroideal
8 Replies
5. Shell Programming and Scripting
Dear All,
Good day, can any of you help me in the following problem:
I need to find the perl equivalent for the following commandline
grep characters |awk '{print \$2}'Expecting your reply and thanks in advance.
Warm regards
Fredrick. (4 Replies)
Discussion started by: Fredrick
4 Replies
6. UNIX for Dummies Questions & Answers
Hi everybody,
i've been googling for ages now and gotten kinda desperate... The question, however, might be rather trivial for the experts: What is it exactly, i.e. physically, the POSIX function (for a file) "lseek" does? Does it trigger some kind of synchronization on disk? Is it just for the... (4 Replies)
Discussion started by: Humudituu
4 Replies
7. UNIX for Dummies Questions & Answers
I tried to use lseek system call to determine the number of bytes in a file. To do so, I used open system call with O_APPEND flag to open a file. As lseek returns the current offset so I called lseek for opened file with offset as zero and whence as SEEK_CUR. So I guess it must return the number of... (3 Replies)
Discussion started by: Deepak Raj
3 Replies
8. Programming
I think both write at the end of the file ......
but is there a sharp difference between those 2 instruction .....
thank you
this is my 3rd question today forgive me :D (1 Reply)
Discussion started by: fwrlfo
1 Replies
9. AIX
Hi,
We are facing issues while backing up our 1205 GB filesystem on LTO5 Tape. During backup the "backup: The lseek call failed." messages were generated, I want to know why these messages were generating
AIX version is: 6100-08-00-0000
backup: The date of this level 0 backup is Mon Mar 11... (4 Replies)
Discussion started by: m_raheelahmed
4 Replies
10. Programming
The following code:
int fd;
if (fd = open("mem", O_RDONLY) == -1)
return 1;
if (lseek(fd, 0, SEEK_SET) == -1) {
char *buf = malloc(512);
buf = strerror(errno);
printf("%s\n", buf);
return 1;
}
always returns with "illegal seek"... (2 Replies)
Discussion started by: Sir_Tomasz
2 Replies
LEARN ABOUT MINIX
lseek64
LSEEK64(3) Linux Programmer's Manual LSEEK64(3)
NAME
lseek64 - reposition 64-bit read/write file offset
SYNOPSIS
#define _LARGEFILE64_SOURCE /* See feature_test_macros(7) */
#include <sys/types.h>
#include <unistd.h>
off64_t lseek64(int fd, off64_t offset, int whence);
DESCRIPTION
The lseek(2) family of functions reposition the offset of the open file associated with the file descriptor fd to offset bytes relative to
the start, current position, or end of the file, when whence has the value SEEK_SET, SEEK_CUR, or SEEK_END, respectively.
For more details, return value, and errors, see lseek(2).
Four interfaces are available: lseek(2), lseek64(), llseek(2), and _llseek(2).
lseek()
Prototype:
off_t lseek(int fd, off_t offset, int whence);
lseek(2) uses the type off_t. This is a 32-bit signed type on 32-bit architectures, unless one compiles with
#define _FILE_OFFSET_BITS 64
in which case it is a 64-bit signed type.
lseek64()
Prototype:
off64_t lseek64(int fd, off64_t offset, int whence);
The library routine lseek64() uses a 64-bit type even when off_t is a 32-bit type. Its prototype (and the type off64_t) is available only
when one compiles with
#define _LARGEFILE64_SOURCE
The function lseek64() is available since glibc 2.1, and is defined to be an alias for llseek().
llseek()
Prototype:
loff_t llseek(int fd, loff_t offset, int whence);
The type loff_t is a 64-bit signed type. The library routine llseek() is available in glibc and works without special defines. However,
the glibc headers do not provide a prototype. Users should add the above prototype, or something equivalent, to their own source. When
users complained about data loss caused by a miscompilation of e2fsck(8), glibc 2.1.3 added the link-time warning
"the `llseek' function may be dangerous; use `lseek64' instead."
This makes this function unusable if one desires a warning-free compilation.
_llseek()
On 32-bit architectures, this is the system call that is used to implement all of the above functions. The prototype is:
int _llseek(int fd, off_t offset_hi, off_t offset_lo,
loff_t *result, int whence);
For more details, see llseek(2).
64-bit systems don't need an _llseek() system call. Instead, they have an lseek(2) system call that supports 64-bit file offsets.
ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7).
+----------+---------------+---------+
|Interface | Attribute | Value |
+----------+---------------+---------+
|lseek64() | Thread safety | MT-Safe |
+----------+---------------+---------+
SEE ALSO
llseek(2), lseek(2)
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/.
Linux 2017-09-15 LSEEK64(3)