Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Unix grep/test command
Top Forums UNIX for Dummies Questions & Answers Unix grep/test command Post 302139759 by robotronic on Tuesday 9th of October 2007 05:29:35 AM
Old 10-09-2007
On Solaris you can use:

Code:
echo "12345678" | /usr/xpg4/bin/grep -Eq "^[0-9]{8}$"

In any case, you must use a tool which supports extended regular expressions to use the above regex.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

unix grep command

I need to seach all strings that matches "if ; then" in all files If i put grep "if ; then" *.* it is not giving any result (1 Reply)
Discussion started by: pmsuper
1 Replies

2. Shell Programming and Scripting

Using grep in a test/if statement

Okay, well this is more or less my first attempt at writing a shell script. Anyways, here's my code: cd ${PATH} if then rm ${FILE} ./anotherScript else exit 1 fi exit 1 Anyways, it's a pretty simple script that is supposed to search for the... (4 Replies)
Discussion started by: cbo0485
4 Replies

3. Shell Programming and Scripting

Using grep inside a test

Hi, I want to use grep inside a test statement, but I am getting an error message. Two variables testvarNum=5 testvarNonNum=x echo $testvarNum | grep * The result of this is as follows: 5 However, when I try the following (i.e. to test if the variable is numeric or non-numeric):... (3 Replies)
Discussion started by: dkieran
3 Replies

4. Shell Programming and Scripting

grep functions, how to test if succeeded

Hello ...again. I am stuck on this part, I have a loop with processes an operations file. and calls different functions depending on what is in loop, which processes a database file... #so far my add function works as intended add() { ...blah blah; } # delete is kinda working... (13 Replies)
Discussion started by: gcampton
13 Replies

5. Shell Programming and Scripting

Test command in UNIX

Hi Team, -rwxr-xr-x 1 kmani00 system 9 Nov 08 03:29 tempfile.txt -rwxrwxrwx 1 kmani00 devgrp 0 Nov 08 03:32 testfile.txt by exec the following command, i did not get any output. > test -s tempfile.txt > a=`test -s tempfile.txt` > echo $a > by exec the... (4 Replies)
Discussion started by: kmanivan82
4 Replies

6. Shell Programming and Scripting

Ksh: Test UNIX command without $? everytime

Hello all, working on Solaris 10 in ksh. Basicly, in my function, i'm trying to test that all my unix cmd's are true (exit status 0) else you flag the rcControlRule to 1 without going into spagetti mode code testing every $? in a if statement. The mdb is probably a little tricky cause it... (3 Replies)
Discussion started by: maverick72
3 Replies

7. Shell Programming and Scripting

Grep/print/ a test file

cat abc.txt Filename: SHA_AED_Monthly_SNR_20150331.txt.gz Data Format: ASCII with carriage returns and linefeeds Compression: GZIP GZIP Bytes: 36893068 Unzipped Bytes : 613794510 Records: 851310 Record Length: 738 Blocksize: 32472 Filename: SHA_AED_SNR_ChangeLog_20150331.txt.gz Data... (16 Replies)
Discussion started by: dotran
16 Replies

8. Shell Programming and Scripting

Please help on UNIX grep command for numbers

I have a list of files like below, Do we have grep command to find files? If i grep 03874 it should display the file 3874, Grep command should ignore 0 at the beginning. There could be more many leading 0's in filename. $ ls -ltr total 5 -rw-r--r-- 1 mqm mqm 15 Feb 19 17:07 4769... (3 Replies)
Discussion started by: prince1987
3 Replies

9. UNIX for Beginners Questions & Answers

Help with UNIX test and wc Command

I want to xheck if a file exists that uses wildcards as only the partial filename is known using the test Command, and when it exists then output just the number of lines in the file... do not include the filename. Then this output, is it captured by the CommandOutput or the ReturnValue as I want... (2 Replies)
Discussion started by: dsinco
2 Replies

10. Shell Programming and Scripting

Using grep with test and without using [[ ]]

As an exercise, I'm trying to re-write this code without the compound square brackets, using grep and test. Need to know what to do about the "equal-tilde". #!/bin/bash # test-integer2: evaluate the value of an integer. INT=-5 if +$ ]]; then if ; then echo "INT is zero." else if ; then... (17 Replies)
Discussion started by: Xubuntu56
17 Replies

LEARN ABOUT OPENSOLARIS

fgrep

fgrep(1)							   User Commands							  fgrep(1)

NAME

       fgrep - search a file for a fixed-character string

SYNOPSIS

       /usr/bin/fgrep [-bchilnsvx] -e pattern_list [file...]

       /usr/bin/fgrep [-bchilnsvx] -f file [file...]

       /usr/bin/fgrep [-bchilnsvx] pattern [file...]

       /usr/xpg4/bin/fgrep [-bchilnqsvx] -e pattern_list [-f file]
	    [file...]

       /usr/xpg4/bin/fgrep [-bchilnqsvx] [-e pattern_list] -f file
	    [file...]

       /usr/xpg4/bin/fgrep [-bchilnqsvx] pattern [file...]

DESCRIPTION

       The  fgrep (fast grep) utility searches files for a character string and prints all lines that contain that string. fgrep is different from
       grep(1) and from egrep(1) because it searches for a string, instead of searching for a pattern that matches an  expression.  fgrep  uses  a
       fast and compact algorithm.

       The characters $, *, [, ^, |, (, ), and  are interpreted literally by fgrep, that is, fgrep does not recognize full regular expressions as
       does egrep. These characters have special meaning to the shell. Therefore, to be safe, enclose the entire string within single quotes (a').

       If no files are specified, fgrep assumes standard input. Normally, each line that is found is copied to the standard output. The file  name
       is printed before each line that is found if there is more than one input file.

OPTIONS

       The following options are supported for both /usr/bin/fgrep and /usr/xpg4/bin/fgrep:

       -b		  Precedes each line by the block number on which the line was found. This can be useful in locating block numbers by con-
			  text. The first block is 0.

       -c		  Prints only a count of the lines that contain the pattern.

       -e pattern_list	  Searches for a string in pattern-list. This is useful when the string begins with a -.

       -f pattern-file	  Takes the list of patterns from pattern-file.

       -h		  Suppresses printing of files when searching multiple files.

       -i		  Ignores upper/lower case distinction during comparisons.

       -l		  Prints the names of files with matching lines once, separated by new-lines. Does not repeat the names of files when  the
			  pattern is found more than once.

       -n		  Precedes each line by its line number in the file. The first line is 1.

       -s		  Works silently, that is, displays nothing except error messages. This is useful for checking the error status.

       -v		  Prints all lines except those that contain the pattern.

       -x		  Prints only lines that are matched entirely.

   /usr/xpg4/bin/fgrep
       The following options are supported for /usr/xpg4/bin/fgrep 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.

OPERANDS

       The following operands are supported:

       file    Specifies a path name of a file to be searched for the patterns. If no file operands are specified,  the  standard  input  will	be
	       used.

   /usr/bin/fgrep
       pattern	  Specifies a pattern to be used during the search for input.

   /usr/xpg4/bin/fgrep
       pattern	  Specifies  one  or  more  patterns to be used during the search for input. This operand is treated as if it were specified as -e
		  pattern_list.

USAGE

       See largefile(5) for the description of the behavior of fgrep 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 fgrep:  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/fgrep
       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+

   /usr/xpg4/bin/fgrep
       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWxcu4			   |
       +-----------------------------+-----------------------------+
       |CSI			     |Enabled			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       ed(1), egrep(1), grep(1), sed(1), sh(1), attributes(5), environ(5), largefile(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 tradeoffs.

       Lines are limited only by the size of the available virtual memory.

   /usr/xpg4/bin/fgrep
       The  /usr/xpg4/bin/fgrep  utility  is identical to /usr/xpg4/bin/grep -F (see grep(1)). Portable applications should use /usr/xpg4/bin/grep
       -F.

SunOS 5.11							    24 Mar 2006 							  fgrep(1)
All times are GMT -4. The time now is 08:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy