06-15-2006
The filesystem knows exactly how many bytes are in the file - when your process reads the file, the kernel keeps track of the location with a file pointer. When the file pointer reaches the offset = length of file, the system stops advancing the file pointer = EOF.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I'd like to access a windows directory from aix with samba client.
To allow direct access (not interactive), i'm using EOF like:
smbclient \\\\winserver\\windir 'passwd' -U usersmb << EOF
cd subwindir
put myfile
EOF
The access is correct but does somebody know how to trap errors... (1 Reply)
Discussion started by: jo_aze
1 Replies
2. Shell Programming and Scripting
Hello, you are an awesome crowd! You answered my last questions, thank you sooo much!
I am trying to write a korn shell script that will record the memory my application is using (HP-UX B.11.11) and I have this:
if (( $APP > $THRESHOLD ))
then
echo "Warning message will display"
cat... (2 Replies)
Discussion started by: satraver
2 Replies
3. Shell Programming and Scripting
How to check for a premature EOF in a regular file in a shell/perl script?
I want to check if I have received a complete file or not.
Thanks,
Rahul. (12 Replies)
Discussion started by: rahulrathod
12 Replies
4. UNIX for Dummies Questions & Answers
I have written this code:
code
echo 'Now choose the file or files you want to merge your input with: \c'
read filenames
filelist=""
for file in $filenames; do
filelist="$filelist $file"
done
echo "Now that you've chosen these files ($filelist), please start typing: "
until ; do
paste -... (2 Replies)
Discussion started by: fiol73
2 Replies
5. Shell Programming and Scripting
hi,
in a shell script i came accross the following bit of code
1.shift $(($OPTIND - 1))
2.if ; then
3. cat << EOF >&2
4.Usage: $0 lockfilename
5.EOF
6. exit 1
7.fi
I am not able to understand the meaning of lines(1,3,5).
Can any one of u tell me the purpose of above said lines.... (1 Reply)
Discussion started by: ravi raj kumar
1 Replies
6. UNIX for Dummies Questions & Answers
Hello all,
I have unix file that ends with the following EOF '9999999999'
I want to remove the '\n' character after EOF. What is the command that should be included in the script, before sending the file?
will this work:
$ echo "<99999999999>\c" >> <filename>
thanks in advance. (3 Replies)
Discussion started by: priya12
3 Replies
7. Shell Programming and Scripting
I'm trying to connect to oracle with the following code in the script:
checksqlerror{
if
echo $1
exit
fi
}
$SQLPLUS username/password@schemaname
checksqlerror "failed to connect to oracle"
If I'm passing wrong schema name,instead of executing checksqlerror it stops and expects user... (2 Replies)
Discussion started by: BhawanaAggarwal
2 Replies
8. Programming
How can I write EOF into a file?
I tryed to do as follows:
size=sizeof(EOF);
end_of_file=EOF;
write(fdMutexRichieste, &end_of_file, size);
But it does non work correctly,
becouse in the next cicle (using lseek(..., SEEK_END) of my code it seems to ignore my EOF and use the LAST... (5 Replies)
Discussion started by: DNAx86
5 Replies
9. Shell Programming and Scripting
Hey!
Can I write a routine that allows me to in a txt file check line by line until the end of file?
something like
until do
---some code---
done
maybe it is a stupid question but I never learned shell scripts and I need this :p
thanks in advance (1 Reply)
Discussion started by: ruben.rodrigues
1 Replies
10. Shell Programming and Scripting
Hi friends ,
I am confused with << EOF
EOF
Most of the cases I found
sqlplus $db_conn_str << EOF
some sql staments
EOF
another exapmle is
#!/bin/sh
echo -n 'what is the value? '
read value
sed 's/XXX/'$value'/' <<EOF
The value is XXX
EOF (1 Reply)
Discussion started by: imipsita.rath
1 Replies
END(3) Linux Programmer's Manual END(3)
NAME
etext, edata, end - end of program segments
SYNOPSIS
extern etext;
extern edata;
extern end;
DESCRIPTION
The addresses of these symbols indicate the end of various program segments:
etext This is the first address past the end of the text segment (the program code).
edata This is the first address past the end of the initialized data segment.
end This is the first address past the end of the uninitialized data segment (also known as the BSS segment).
CONFORMING TO
Although these symbols have long been provided on most UNIX systems, they are not standardized; use with caution.
NOTES
The program must explicitly declare these symbols; they are not defined in any header file.
On some systems the names of these symbols are preceded by underscores, thus: _etext, _edata, and _end. These symbols are also defined for
programs compiled on Linux.
At the start of program execution, the program break will be somewhere near &end (perhaps at the start of the following page). However,
the break will change as memory is allocated via brk(2) or malloc(3). Use sbrk(2) with an argument of zero to find the current value of
the program break.
EXAMPLE
When run, the program below produces output such as the following:
$ ./a.out
First address past:
program text (etext) 0x8048568
initialized data (edata) 0x804a01c
uninitialized data (end) 0x804a024
Program source
#include <stdio.h>
#include <stdlib.h>
extern char etext, edata, end; /* The symbols must have some type,
or "gcc -Wall" complains */
int
main(int argc, char *argv[])
{
printf("First address past:
");
printf(" program text (etext) %10p
", &etext);
printf(" initialized data (edata) %10p
", &edata);
printf(" uninitialized data (end) %10p
", &end);
exit(EXIT_SUCCESS);
}
SEE ALSO
objdump(1), readelf(1), sbrk(2), elf(5)
COLOPHON
This page is part of release 3.53 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/.
GNU
2008-07-17 END(3)