Sponsored Content
Top Forums Shell Programming and Scripting what is wrong with this expr line Post 302356198 by shadow_boi on Friday 25th of September 2009 12:29:13 AM
Old 09-25-2009
what is wrong with this expr line

It keeps giving me expr syntax error.
Code:
expr "${etherline[*]}" : ’.*no match found’ 2>&1 >/dev/null

Thanks in advance.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Whats wrong with this 5 line script!

Hi #!/bin/sh user=$1 if " -eq 0 ] echo "No" else echo "Yes" fi I'm not quite sure whats wrong with this but I know its something silly. Any ideas? Thanks (9 Replies)
Discussion started by: c19h28O2
9 Replies

2. UNIX for Dummies Questions & Answers

What's wrong with this line: if ${TEST:?} ; then echo empty; fi

I want to print "empty" if $TEST is empty. TEST= if ${TEST:?} ; then echo empty; fi But it doesn't work. What's wrong? (2 Replies)
Discussion started by: meili100
2 Replies

3. Shell Programming and Scripting

Whats wrong with this line?

I have a file $I_FILE that I need to filter and store the 1st and the 9th columns in another file $O_FILE. With this in Perl, system ("awk -F, '{print \$1, \$9}' \$I_FILE | sed '\/^\$\/d' > O_FILE"); I get: 4096045055 The first line in I_FILE is:... (5 Replies)
Discussion started by: looza
5 Replies

4. Shell Programming and Scripting

what is wrong with this line?

system ("$ssh '$perf_stats' < temp_pipe 2>&1 &"); I need to start and interact with my executable defined by perf_stats on a remote machine but not change my command line to that of the remote machine. temp_pipe is a node created by mknod -f temp_pipe (6 Replies)
Discussion started by: looza
6 Replies

5. Shell Programming and Scripting

whats wrong with this line using perl

E:\>perl -00ne 'push @a,"$_\0$ARGV\n";END{print reverse split/\0/ for sort @a}' file1-obj_prof.out.txt file2-obj_prof.out.txt' Can't find string terminator "'" anywhere before EOF at -e line 1. (6 Replies)
Discussion started by: richsark
6 Replies

6. Shell Programming and Scripting

What's wrong with this command line pls?

I executed the following command and got Arg List too long. find /dir1/dir2/LOG_* -prune -type f -mtime +3 -exec echo {} \; What's that about? (2 Replies)
Discussion started by: bbbngowc
2 Replies

7. Shell Programming and Scripting

SED to delete last word on line...what's wrong?

I have a line that gets pulled from a database that has a variable number of fields, fields can also be of a variable size. Each field has a variable number of spaces between them so there is no 'defined' delimiter. The LastData block is always a single word. What I want to do is delete the... (2 Replies)
Discussion started by: Bashingaway
2 Replies

8. Shell Programming and Scripting

What is wrong with tiny (g)awk line ??

Hi I wish to capitalize the first letter or every word in a text file with: gawk '{$0=gensub(/(\w)(\w*)/,toupper("\\1")"\\2","g");}' file.txtBut it doesn't work...: target: bla test Test TEST yes nO Yes yes restult: bla test Test TEST yes nO Yes yes any idea? thanks (11 Replies)
Discussion started by: louisJ
11 Replies

9. Shell Programming and Scripting

what's wrong with my awk line?

] && { echo "The free mem need to be more than 2G" } (3 Replies)
Discussion started by: yanglei_fage
3 Replies

10. Shell Programming and Scripting

Expr: non-numeric argument syntax error on line 1, teletype

Hi, I tried to look up the issue i'm experiencing, but i'm confused what's wrong with my script. After executing the script I'm getting the following error expr: non-numeric argument syntax error on line 1, teletype After some research, it seems that the problem relates to bc. I have... (1 Reply)
Discussion started by: nms
1 Replies
EXPR(1) 						    BSD General Commands Manual 						   EXPR(1)

NAME
expr -- evaluate expression SYNOPSIS
expr expression DESCRIPTION
The expr utility evaluates expression and writes the result on standard output. All operators are separate arguments to the expr utility. Characters special to the command interpreter must be escaped. Operators are listed below in order of increasing precedence. Operators with equal precedence are grouped within { } symbols. expr1 | expr2 Returns the evaluation of expr1 if it is neither an empty string nor zero; otherwise, returns the evaluation of expr2. expr1 & expr2 Returns the evaluation of expr1 if neither expression evaluates to an empty string or zero; otherwise, returns zero. expr1 {=, >, >=, <, <=, !=} expr2 Returns the results of integer comparison if both arguments are integers; otherwise, returns the results of string comparison using the locale-specific collation sequence. The result of each comparison is 1 if the specified relation is true, or 0 if the relation is false. expr1 {+, -} expr2 Returns the results of addition or subtraction of integer-valued arguments. expr1 {*, /, %} expr2 Returns the results of multiplication, integer division, or remainder of integer-valued arguments. expr1 : expr2 The ``:'' operator matches expr1 against expr2, which must be a regular expression. The regular expression is anchored to the begin- ning of the string with an implicit ``^''. If the match succeeds and the pattern contains at least one regular expression subexpression ``(...)'', the string corresponding to ``1'' is returned; otherwise the matching operator returns the number of characters matched. If the match fails and the pattern contains a regular expression subexpression the null string is returned; otherwise 0. ( expr ) Parentheses are used for grouping in the usual manner. Additionally, the following keywords are recognized: length expr Returns the length of the specified string in bytes. Operator precedence (from highest to lowest): 1. parentheses 2. length 3. ``:'' 4. ``*'', ``/'', and ``%'' 5. ``+'' and ``-'' 6. compare operators 7. ``&'' 8. ``|'' EXIT STATUS
The expr utility exits with one of the following values: 0 the expression is neither an empty string nor 0. 1 the expression is an empty string or 0. 2 the expression is invalid. >2 an error occurred (such as memory allocation failure). EXAMPLES
1. The following example adds one to the variable a. a=`expr $a + 1` 2. The following example returns zero, due to subtraction having higher precedence than '&' operator. expr 1 '&' 1 - 1 3. The following example returns the filename portion of a pathname stored in variable a. expr /$a : '.*/(.*)' 4. The following example returns the number of characters in variable a. expr $a : '.*' COMPATIBILITY
This implementation of expr internally uses 64 bit representation of integers and checks for over- and underflows. It also treats / (divi- sion mark) and option '--' correctly depending upon context. expr on other systems (including NetBSD up to and including NetBSD 1.5) might not be so graceful. Arithmetic results might be arbitrarily limited on such systems, most commonly to 32 bit quantities. This means such expr can only process values between -2147483648 and +2147483647. On other systems, expr might also not work correctly for regular expressions where either side contains single forward slash, like this: expr / : '.*/(.*)' If this is the case, you might use // (double forward slash) to avoid confusion with the division operator: expr "//$a" : '.*/(.*)' According to IEEE Std 1003.2 (``POSIX.2''), expr has to recognize special option '--', treat it as an end of command line options and ignore it. Some expr implementations don't recognize it at all, others might ignore it even in cases where doing so results in syntax error. There should be same result for both following examples, but it might not always be: 1. expr -- : . 2. expr -- -- : . Although NetBSD expr handles both cases correctly, you should not depend on this behavior for portability reasons and avoid passing bare '--' as first argument. STANDARDS
The expr utility conforms to IEEE Std 1003.2 (``POSIX.2''). The length keyword is an extension for compatibility with GNU expr. AUTHORS
Original implementation was written by J.T. Conklin <jtc@NetBSD.org>. It was rewritten for NetBSD 1.6 by Jaromir Dolecek <jdolecek@NetBSD.org>. NOTES
The empty string ``'' cannot be matched with the intuitive: expr '' : '$' The reason is that the returned number of matched characters (zero) is indistinguishable from a failed match, so this returns failure. To match the empty string, use something like: expr x'' : 'x$' BSD
April 20, 2004 BSD
All times are GMT -4. The time now is 07:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy