10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hey guys, my first post on UNIX Forums(much overdue IMO)!
I've got this bit of code that doesn't seem to be working correctly for an Android app I'm working on:
"screen -S gmod1 -p 0 -X stuff " & "" & command.text & "`echo -ne '\015'`"""
Basically it types command.text(variable determined... (4 Replies)
Discussion started by: stingwraith
4 Replies
2. Shell Programming and Scripting
Greetings!
Here's what I believe is a "simple one" for the community tonight ;)
What I'm trying to do is assign a "true/false" value to a variable depending upon whether a named process (some-process) exists; and then test for this value in the succeeding logic. I banged my head against the... (2 Replies)
Discussion started by: LinQ
2 Replies
3. Programming
Hallo everybody,
I have a following problem - I'm doing a map funciont to fill in a HTML table and I want to use some radiobutton groups. Unfortunatelly, they are grouped by names, so I have to add some "counter" that will divide one row from another, and I'm using CGI.pm for generating the... (3 Replies)
Discussion started by: duskos
3 Replies
4. Shell Programming and Scripting
I am writing a perl script to tar multiple files (in unix) from a given directory to a given output directory. I do NOT want the file path included in the tar, so I've flagged the -C option. Example:
tar -cvf tar/1.tar -C htmp/source/ 1-1-1.xml
However, I need to do this for a number of target... (3 Replies)
Discussion started by: michanjohns
3 Replies
5. UNIX for Advanced & Expert Users
Hello,
I need to create an snmp.comf file that defines 2 IPs to the same community string.
Do I need to have 2 community strings with the same name and diff't IPs?
Or should I have 1 string and list the IPs? (comma seperated?)
Example:
rocommunity EC_8000_RO
arguments EC_8000_RO... (2 Replies)
Discussion started by: felbvts
2 Replies
6. Programming
Hello, the following is generating a error at the line "tmprintf(&tmBundle, _TMC("{0}"),Prompt);"... a bit lost as I am diving into this debug...
Thank you in advance...
int H_YesNo(TMCHAR *Prompt, int DefVal)
{
TMCHAR YesNo = '\0';
tmprintf(&tmBundle, _TMC("{0}"),Prompt);
while... (3 Replies)
Discussion started by: reelflytime
3 Replies
7. Shell Programming and Scripting
Hi
I use awk command to delete the first blanc line of a file:
awk '/^$/ && !f{f=1;next}1' infile > outfile
can somebody please explain me what the last "1'" in !f{f=1;next}1' stands for... Thansk a lot -A (3 Replies)
Discussion started by: aoussenko
3 Replies
8. UNIX for Dummies Questions & Answers
There are are lots of examples of piping output FROM the 'ls' command TO another command, but how does one pipe output TO the 'ls -l' command?
For example, use 'which' to find a file, then use 'ls -l' to view the permissions, groups, etc. in a single step:
which <filename> | ls -l
returns... (4 Replies)
Discussion started by: johne1
4 Replies
9. UNIX for Dummies Questions & Answers
Hi,
Have to check file names in some given directory.
SO, What is the right syntax here:
*$3*=="'$object_list'" - just wanted to check if $3 is in the object_list.
And also, Do I need so many quotes around? (5 Replies)
Discussion started by: Leo_NN
5 Replies
10. Shell Programming and Scripting
Hi there could someone explain what is happening in the following function/statement for me, im just a little confused
code = 'BEGIN{FS=","}
{
printf ("%-11s,%s%s%s,%07.2f,%14s,%-3s\n",$1,substr($2,9,2),substr($2,6,2),substr($
2,3,2),$9,$10,$12)
}
this function is called later in the... (2 Replies)
Discussion started by: hcclnoodles
2 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 and operands must be passed as separate arguments. Several of the operators have special meaning to command interpreters and
must therefore be quoted appropriately. All integer operands are interpreted in base 10 and must consist of only an optional leading minus
sign followed by one or more digits.
Arithmetic operations are performed using signed integer math with a range according to the C intmax_t data type (the largest signed integral
type available). All conversions and operations are checked for overflow. Overflow results in program termination with an error message on
stdout and with an error status.
Operators are listed below in order of increasing precedence; all are left-associative. Operators with equal precedence are grouped within
symbols '{' and '}'.
expr1 | expr2
Return the evaluation of expr1 if it is neither an empty string nor zero; otherwise, returns the evaluation of expr2 if it is not an
empty string; otherwise, returns zero.
expr1 & expr2
Return the evaluation of expr1 if neither expression evaluates to an empty string or zero; otherwise, returns zero.
expr1 {=, >, >=, <, <=, !=} expr2
Return 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
Return the results of addition or subtraction of integer-valued arguments.
expr1 {*, /, %} expr2
Return the results of multiplication, integer division, or remainder of integer-valued arguments.
expr1 : expr2
The ``:'' operator matches expr1 against expr2, which must be a basic regular expression. The regular expression is anchored to the
beginning 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.
Parentheses are used for grouping in the usual manner.
The expr utility makes no lexical distinction between arguments which may be operators and arguments which may be operands. An operand which
is lexically identical to an operator will be considered a syntax error. See the examples below for a work-around.
The syntax of the expr command in general is historic and inconvenient. New applications are advised to use shell arithmetic rather than
expr.
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.
EXAMPLES
o The following example (in sh(1) syntax) adds one to the variable a:
a=$(expr $a + 1)
o This will fail if the value of a is a negative number. To protect negative values of a from being interpreted as options to the expr
command, one might rearrange the expression:
a=$(expr 1 + $a)
o More generally, parenthesize possibly-negative values:
a=$(expr ( $a ) + 1)
o With shell arithmetic, no escaping is required:
a=$((a + 1))
o This example prints the filename portion of a pathname stored in variable a. Since a might represent the path /, it is necessary to pre-
vent it from being interpreted as the division operator. The // characters resolve this ambiguity.
expr "//$a" : '.*/(.*)'
o With modern sh(1) syntax,
"${a##*/}"
expands to the same value.
The following examples output the number of characters in variable a. Again, if a might begin with a hyphen, it is necessary to prevent it
from being interpreted as an option to expr, and a might be interpreted as an operator.
o To deal with all of this, a complicated command is required:
expr ( "X$a" : ".*" ) - 1
o With modern sh(1) syntax, this can be done much more easily:
${#a}
expands to the required number.
SEE ALSO
sh(1), test(1)
STANDARDS
The expr utility conforms to IEEE Std 1003.1-2008 (``POSIX.1'').
The extended arithmetic range and overflow checks do not conflict with POSIX's requirement that arithmetic be done using signed longs, since
they only make a difference to the result in cases where using signed longs would give undefined behavior.
According to the POSIX standard, the use of string arguments length, substr, index, or match produces undefined results. In this version of
expr, these arguments are treated just as their respective string values.
BSD
September 9, 2010 BSD