Not a problem
First section is just to move the list of groups we are splitting into tp the top in case you want to change it later.
We then take a command line argument for the file to search over and store it.
Code:
#!/bin/sh
MYGROUPS="OT OM OA"
file_to_sort=$1
Next we perform the loop below for each group (ie once per item in $MYGROUPS)
The egrep (a version of grep that understand regular expressions better) is looking for lines that end in our group identifier (the '\$' means 'end of line') in the file. The list that comes out is then passed to sort to alphabetise it.
Code:
for group in $MYGROUPS
do
echo "$group"
echo "--"
egrep "${group}\$" $file_to_sort | sort
echo ""
done
The next part it completely optional, I just included it in case you might want to throw up a warning listing any lines that didn't match one of the groups you are looking for. You could add an 'exit 1' line just before the 'fi' at the end if you want to have it produce an error status when this happens too.
The first egrep is looking to see if there is any output left after grepping out (via the -v flag) any of the groups we are looking for.
It builds the regular expression based on the MYGROUPS variable by replacing the spaces with '|' symbols. This way it is doing an egrep -v "(OT|OM|OA)\$" over the file (ie list all output that doesn't end with Ot, OM or OA).
The first time is to see if we find any (it just throws it away), if so, it prints the header than does it again to the screen. It's a shame to do the search twice, you could store the output from the first run and just display it later but I don't like generating temporary files and was being a bit lazy
Code:
# Catch any unexpected input (if you want that)
if egrep -v "(`echo $MYGROUPS | sed 's/ /\|/g'`)\$" $file_to_sort > /dev/null
then
echo "*** UNEXPECTED ***"
egrep -v "(`echo $MYGROUPS | sed 's/ /\|/g'`)\$" $file_to_sort
fi
I've actually seen a couple of minor mistakes I made in that last part too - fixed in teh above version. The first grep was missing the brackets to group the regular expression and both greps were missing the \$ to indicate that it should be looking at the end of the line.
I'm running against a file with 1008 records like this, all beginning '4760 Slave':
4760 Slave,7,3607 ,GL ,200605,11320024 , ,GBP ,X00033
,AI80190 ... (1 Reply)
this one is a bit tricky:
host16 /etc/passwd changed Thu Jan 3 16:39:48
host3 /etc/group changed Thu Jan 3 16:39:48
host2 /etc/services changed Thu Jan 3 16:39:48
host10 /etc/group changed Thu Jan 10 09:59:01
host11 /etc/group changed Thu Jan 3 18:55:38
host17 /etc/group changed Thu Jan... (9 Replies)
Hi
I have a file that is a fdupes output. I'd like to sort the duplicated file by size. The format file is the following:
5996544 bytes each:
/path1/to/file1.jpg
/path2/to/file1.jpg
/pathx/to/file1.jpg
... random number of lines
/path999/to/file1.jpg
591910 bytes each:... (2 Replies)
Hi All,
I would like to ask help on how can i achieve below output.
Inputfile:
Oct11,apa1-daily,01:25:01
Oct11,apa2-daily,01:45:23
Oct12,apa1-daily,02:30:11
Oct12,apa2-daily,01:55:01
Oct13,apa1-off,01:43:34
Oct13,apa2-off,01:22:04
Desired output:
Clients ... (3 Replies)
Hi all! I have a comma delimited file and I'm sorting it based on fields 6, 8 and 10. The following does the job:
sort -t, -nk6,10 unsorted.txt -o sorted.txt
What I need to do now is to write every row containing same values on fields 6, 8 and 10 to a different file.
Any ideas on how to do... (2 Replies)
Now I van sort in hour-minute-second. I need in seconds
ps -eo pid,etime,args --sort=start_time | grep bash
Sample Output
15064 03:23 -bash
I need in 03:23 in seconds (1 Reply)
with a command i get a long list (example) and the entrys are intended.
DName=AAAAA
DName=AAAAA
lba=838,860,800
label=ftw_1
DName=BBBBB
DName=BBBBB
lba=838,860,800
label=ftw_2
DName=CCCCC
... (3 Replies)
Hi,
I am using a command :-
ps -auxwww 2> /dev/null | awk 'match ($0, GIN:*/) {print substr($0, RSTART+3, RLENGTH-3)}' | sort | grep -v -F 'which gives output as
3 aruau
5 asun
4 cgan
Now I need a command which gives me something like this :-
3 aruau
5 asun
4 cgan... (2 Replies)
Hi,
This is one of the thing that am looking for when I post the question on the ps wrapper. It has since been closed as it has taken me too long to post an example.
I have replaced some of the original content of the ps output.
uname -a = SunOS <hostname> 5.11 11.3 sun4v sparc sun4v
... (1 Reply)
Discussion started by: newbie_01
1 Replies
LEARN ABOUT BSD
egrep
GREP(1) General Commands Manual GREP(1)NAME
grep, egrep, fgrep - search a file for a pattern
SYNOPSIS
grep [ option ] ... expression [ file ] ...
egrep [ option ] ... [ expression ] [ file ] ...
fgrep [ option ] ... [ strings ] [ file ]
DESCRIPTION
Commands of the grep family search the input files (standard input default) for lines matching a pattern. Normally, each line found is
copied to the standard output. Grep patterns are limited regular expressions in the style of ex(1); it uses a compact nondeterministic
algorithm. Egrep patterns are full regular expressions; it uses a fast deterministic algorithm that sometimes needs exponential space.
Fgrep patterns are fixed strings; it is fast and compact. The following options are recognized.
-v All lines but those matching are printed.
-x (Exact) only lines matched in their entirety are printed (fgrep only).
-c Only a count of matching lines is printed.
-l The names of files with matching lines are listed (once) separated by newlines.
-n Each line is preceded by its relative line number in the file.
-b Each line is preceded by the block number on which it was found. This is sometimes useful in locating disk block numbers by con-
text.
-i The case of letters is ignored in making comparisons -- that is, upper and lower case are considered identical. This applies to
grep and fgrep only.
-s Silent mode. Nothing is printed (except error messages). This is useful for checking the error status.
-w The expression is searched for as a word (as if surrounded by `<' and `>', see ex(1).) (grep only)
-e expression
Same as a simple expression argument, but useful when the expression begins with a -.
-f file
The regular expression (egrep) or string list (fgrep) is taken from the file.
In all cases the file name is shown if there is more than one input file. Care should be taken when using the characters $ * [ ^ | ( ) and
in the expression as they are also meaningful to the Shell. It is safest to enclose the entire expression argument in single quotes ' '.
Fgrep searches for lines that contain one of the (newline-separated) strings.
Egrep accepts extended regular expressions. In the following description `character' excludes newline:
A followed by a single character other than newline matches that character.
The character ^ matches the beginning of a line.
The character $ matches the end of a line.
A . (period) matches any character.
A single character not otherwise endowed with special meaning matches that character.
A string enclosed in brackets [] matches any single character from the string. Ranges of ASCII character codes may be abbreviated
as in `a-z0-9'. A ] may occur only as the first character of the string. A literal - must be placed where it can't be mistaken as
a range indicator.
A regular expression followed by an * (asterisk) matches a sequence of 0 or more matches of the regular expression. A regular
expression followed by a + (plus) matches a sequence of 1 or more matches of the regular expression. A regular expression followed
by a ? (question mark) matches a sequence of 0 or 1 matches of the regular expression.
Two regular expressions concatenated match a match of the first followed by a match of the second.
Two regular expressions separated by | or newline match either a match for the first or a match for the second.
A regular expression enclosed in parentheses matches a match for the regular expression.
The order of precedence of operators at the same parenthesis level is [] then *+? then concatenation then | and newline.
Ideally there should be only one grep, but we don't know a single algorithm that spans a wide enough range of space-time tradeoffs.
SEE ALSO ex(1), sed(1), sh(1)DIAGNOSTICS
Exit status is 0 if any matches are found, 1 if none, 2 for syntax errors or inaccessible files.
BUGS
Lines are limited to 256 characters; longer lines are truncated.
4th Berkeley Distribution April 29, 1985 GREP(1)
11-12-2007
