Earnstaf,
This part will display entries in current and previous hours:
Code:
typeset -i mCurrHH
typeset -i mPrevHH
mCurrHH=`date +"%H"`
mPrevHH=${mCurrHH}-1
if [ ${mPrevHH} -eq -1 ]; then
mPrevHH=23 ## Assuming 00:00 to 23:59
fi
mFirstPart='^... .. '
egrep "${mFirstPart}${mPrevHH}|${mFirstPart}${mCurrHH}" input_file
Shell Life,
Nice script. That might fit my needs a little better actually. That way I can just cron it to run on the hour and it will find everything for the previous (take out egrep and just grep on ${mPrevHH}.. I notice you use the typeset in a lot of your scripts.. I'll do some reading on that see what I can learn.
Thanks for the input. This forum has been very beneficial to me teaching me scripting... hopefully one day I can contribute as much as you guys do
Edit: Quick question:
What is this part doing?
Code:
mFirstPart='^... .. '
Looks like some sort of regexp matching from the start of the line?? Thanks for your help.
Hello everyone,
This is my first post here and this is the first time I am using UNIX OS (Slackware). I find it really useful and powerful and would like to master it but as you may guess I am expreicing quite a few problems.
I've been reading a few documentations about it and bash this week... (17 Replies)
I would like some advice on how to logically put together a script to handle a daily task of data gathering for the following problem.
I have two files, file1 has 125,000 records that I cut and remove unwanted fields through scripts and cron. In file2, I have 25000 records that has the same... (4 Replies)
Alright, I feel like I have a pretty good basic knowledge of shell scripting, but this one is throwing me for a loop. I know I've seen something similar done with awk, but I couldn't find it with the search function.
I've grepped through my log file and get results like this:
--... (14 Replies)
Hello,
I have this script running on cron every 20 minutes.
By 12pm daily, our system is expecting all input files to be uploaded by the script.
After this cutoff time, the script would still be running though, but i need some kind of alerts/logs to know which input files weren't received for... (1 Reply)
I already have a solution to my problem, but I'm looking to see if it can be made more succinct and faster. The problem: given a list, as shown below, extract the pathname for any file in a directory named 'ample' and return it's index into the list. The index is also in the data itself. Note that... (1 Reply)
Hi folks,
I use following script:-
#!/bin/sh
# cd Linbread
TODAY=`date +"%m%d"`
DATA=`grep $TODAY linbread.dat`
HOUR=`date +"%H"`
if
then TOD="Morning"
elif
then TOD="Afternoon"
else
TOD="Evening"
fi
echo $DATA | gawk -F"|" '{printf("%s\n\n%s",$2,$3)}' > $$tmp
fold -s -w60... (0 Replies)
Greetings all. I have a repository server which receives, without exhaggeration, several million files a week. The majority of these files are in .csv format, which means they're highly compressable. They are spread throughout numerous directories where there are configured monitoring utilities... (4 Replies)
All
I have 2 parent directories - input and output. Each parent has multiple sub-directories...each sub-directory has multiple files. Each parent directory structure is a mirror image of itself
I need to poll the imput directory and if a new file is found, encrypt the file, move the file to... (2 Replies)
Hi,
Not sure whether this is the right place to post it. I decided to post it here 'coz Advanced and Expert users will most likely have the answer to what I am looking for.
I want to backup scripts that I have access to to a tar file file and zip it. At the moment I am creating a directory... (4 Replies)
Discussion started by: newbie_01
4 Replies
LEARN ABOUT OPENSOLARIS
egrep
egrep(1) User Commands egrep(1)NAME
egrep - search a file for a pattern using full regular expressions
SYNOPSIS
/usr/bin/egrep [-bchilnsv] -e pattern_list [file...]
/usr/bin/egrep [-bchilnsv] -f file [file...]
/usr/bin/egrep [-bchilnsv] pattern [file...]
/usr/xpg4/bin/egrep [-bchilnqsvx] -e pattern_list [-f file]
[file...]
/usr/xpg4/bin/egrep [-bchilnqsvx] [-e pattern_list] -f file
[file...]
/usr/xpg4/bin/egrep [-bchilnqsvx] pattern [file...]
DESCRIPTION
The egrep (expression grep) utility searches files for a pattern of characters and prints all lines that contain that pattern. egrep uses
full regular expressions (expressions that have string values that use the full set of alphanumeric and special characters) to match the
patterns. It uses a fast deterministic algorithm that sometimes needs exponential space.
If no files are specified, egrep assumes standard input. Normally, each line found is copied to the standard output. The file name is
printed before each line found if there is more than one input file.
/usr/bin/egrep
The /usr/bin/egrep utility accepts full regular expressions as described on the regexp(5) manual page, except for ( and ), ( and ), {
and }, < and >, and
, and with the addition of:
1. A full regular expression followed by + that matches one or more occurrences of the full regular expression.
2. A full regular expression followed by ? that matches 0 or 1 occurrences of the full regular expression.
3. Full regular expressions separated by | or by a NEWLINE that match strings that are matched by any of the expressions.
4. A full regular expression that can be enclosed in parentheses ()for grouping.
Be careful using the characters $, *, [, ^, |, (, ), and in full regular expression, because they are also meaningful to the shell. It is
safest to enclose the entire full regular expression in single quotes (a'a').
The order of precedence of operators is [], then *?+, then concatenation, then | and NEWLINE.
/usr/xpg4/bin/egrep
The /usr/xpg4/bin/egrep utility uses the regular expressions described in the EXTENDED REGULAR EXPRESSIONS section of the regex(5) manual
page.
OPTIONS
The following options are supported for both /usr/bin/egrep and /usr/xpg4/bin/egrep:
-b Precede each line by the block number on which it was found. This can be useful in locating block numbers by context
(first block is 0).
-c Print only a count of the lines that contain the pattern.
-e pattern_list Search for a pattern_list (full regular expression that begins with a -).
-f file Take the list of full regular expressions from file.
-h Suppress printing of filenames when searching multiple files.
-i Ignore upper/lower case distinction during comparisons.
-l Print the names of files with matching lines once, separated by NEWLINEs. Does not repeat the names of files when the
pattern is found more than once.
-n Precede each line by its line number in the file (first line is 1).
-s Work silently, that is, display nothing except error messages. This is useful for checking the error status.
-v Print all lines except those that contain the pattern.
/usr/xpg4/bin/egrep
The following options are supported for /usr/xpg4/bin/egrep only:
-q Quiet. Does not write anything to the standard output, regardless of matching lines. Exits with zero status if an input line is
selected.
-x Consider only input lines that use all characters in the line to match an entire fixed string or regular expression to be matching
lines.
OPERANDS
The following operands are supported:
file A path name of a file to be searched for the patterns. If no file operands are specified, the standard input is used.
/usr/bin/egrep
pattern Specify a pattern to be used during the search for input.
/usr/xpg4/bin/egrep
pattern Specify one or more patterns to be used during the search for input. This operand is treated as if it were specified as -epat-
tern_list..
USAGE
See largefile(5) for the description of the behavior of egrep when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of egrep: LC_COLLATE, LC_CTYPE, LC_MES-
SAGES, and NLSPATH.
EXIT STATUS
The following exit values are returned:
0 If any matches are found.
1 If no matches are found.
2 For syntax errors or inaccessible files (even if matches were found).
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
/usr/bin/egrep
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|CSI |Not Enabled |
+-----------------------------+-----------------------------+
/usr/xpg4/bin/egrep
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWxcu4 |
+-----------------------------+-----------------------------+
|CSI |Enabled |
+-----------------------------+-----------------------------+
SEE ALSO fgrep(1), grep(1), sed(1), sh(1), attributes(5), environ(5), largefile(5), regex(5), regexp(5), XPG4(5)NOTES
Ideally there should be only one grep command, but there is not a single algorithm that spans a wide enough range of space-time trade-offs.
Lines are limited only by the size of the available virtual memory.
/usr/xpg4/bin/egrep
The /usr/xpg4/bin/egrep utility is identical to /usr/xpg4/bin/grep -E. See grep(1). Portable applications should use /usr/xpg4/bin/grep -E.
SunOS 5.11 24 Mar 2006 egrep(1)
06-18-2007
