I'm writing a small script thats purpose is to validate a single command line argument to make sure it is an integer. Also acceptable are a leading "+" or "-", but no more than one.
Example: "5" "-2" "+4" are all valid
If its invalid I simply print out a message saying so, otherwise I... (2 Replies)
How can i make something like
if (echo "$arg2" | egrep -s '^+\.+km/h+$|^+km/h+$'); then
not to output the value of $arg2 on the screen, evertime i get match it outputs the value of the variable on the screen which i don't need to do. I know for grep its -q option but it doesn't work for egrep.... (2 Replies)
Hi I've been searching google and have not found what egrep -c means. Does anyone know where I can get a cheat sheet or what that -c means?
thanks,
Linda (2 Replies)
Hello,
Why is this not returning files containing the string in the var $files?
files=`ls /dir1/dir_level2/dir_level3 | egrep "catch \["`
files=`ls /dir1/dir_level2/dir_level3` this by itself returns a list of files which I thought could be sent through grep or egrep to look for matches.
... (5 Replies)
Hi Guys,
we have a shell script which basically query the Database which retrieves huge data and use the data with "egrep" .
Now there is some data which contains characters like "abc)" and the same is used like below :
"egrep (.+\|GDPRAB16\|GDPR/11702 96 abc)\|$ temp.txt"
now while... (7 Replies)
Hello,
On Aix 5.2, we changed the parameters tcp_keepinit, tcp_keepintvl and tcp_keepidle with the no command.
tunrestore -R is present in inittab
in the directory /etc/tunables we can clearly see the inclusion of parameters during reboot, including the file lastboot.log
... (0 Replies)
Hi,
I am wondering if it's possible to link multiple patterns with egrep.
Here here is what I am doing :
grep -v ";;" | grep -v ARC_TIME | grep -v \* | grep -v STAS0 Can I do all of this by invoking egrep just once ?
Thanks (4 Replies)
hi,
i'm using egrep -i to search thru some text files for keywords (also stored in a file).
egrep does wildcard search aka %keyword%
as long as the keyword is found, it will be spool to a file
meaning if keyword is 'xyz'
123 aabgdggjxyzslgj
124 xyzgjksgjd
returns
123... (8 Replies)
Discussion started by: bing
8 Replies
LEARN ABOUT DEBIAN
edata
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.44 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)