|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
Conditional IF statement with a wildcard
Post 302549719 by frank_rizzo on Tuesday 23rd of August 2011 09:33:21 PM
08-23-2011
|
|
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
how can i use awk or sed to do a conditional statement, so that
HH:MM
if MM not great than 30 , then MM=00
else MM=30
ie:
10:34 will display 10:30
10:29 will display 10:00
a=$(echo 10:34 | awk ......)
Thanks in advance (10 Replies)
Discussion started by: 3Gmobile
10 Replies
2. Shell Programming and Scripting
can somebody help, what quote i should use in below statement or what wrong of it ?
the 1st (*) is a char, the 2nd and 3rd (*) is a wildcard
if ] && ] && ]
................^ .............^
then
echo "ok"
fi
thanks in advance. (2 Replies)
Discussion started by: 3Gmobile
2 Replies
3. Shell Programming and Scripting
Hi
Does Unix have a conditional statement like Java as follows:
Condition ? Statement1 : Statement2
Thanks (8 Replies)
Discussion started by: lalelle
8 Replies
4. Shell Programming and Scripting
Hi all,
The following code is to find if a list of numbers from one file are within the range in another file.
awk -F, '\
BEGIN {
while ((getline < "file2") > 0)
file2=$3
}
{for (col1 in file2)
if ($0>=30 && $1<=45)
print $0} ' FILE1
But where I have the number 30 and 45, I... (3 Replies)
Discussion started by: dr_sabz
3 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I'm getting a "bad number" error from the following conditional if statement. I understand the results of the grep command are not being treated a an integer but am unsure of the correct syntax. Any help would be appreciated.
if
Thanks (2 Replies)
Discussion started by: dlafa
2 Replies
6. Shell Programming and Scripting
Hi,
I have a script like this:
sample.sh
mapping=$1
if
then
echo "program passed"
fi
I'm running the above script as ./sample.sh pass
The script is not getting executed and says "integer expression expected"
Could anyone kindly help me? (2 Replies)
Discussion started by: badrimohanty
2 Replies
7. Shell Programming and Scripting
Please see the script segment below
for i in $files
do
echo $i
if ; then
case "$1" in
"IE0263"|"IE0264"|"IE0267"|"IE0268")
short_filename=`ls -l $i | cut -c108-136 | sort`
;;
"IE0272"|"IE0273")
short_filename=`ls -l $i | cut... (4 Replies)
Discussion started by: jmahal
4 Replies
8. UNIX for Advanced & Expert Users
I need to implement something like this.
1) search for a file(say *.doc) from a path (say /home/user/temp)
2) if file found & if file size > 0 : yes --> file valid
else : print file not valid.
I am trying to implement something like this, but seems i am terribly wrong somewhere.. ... (1 Reply)
Discussion started by: animesharma
1 Replies
9. Shell Programming and Scripting
I'm trying to make a small script to see if you say a specific word, in bash.
Here is my code so far :
if ]; then
echo "You typed Something Device Something"
fi
exit 0
It does not echo what it should, even if i type something along the lines of "random Device stuff"
Please help,... (2 Replies)
Discussion started by: DuskFall
2 Replies
10. Shell Programming and Scripting
Hi all,
I have a file containing the values that would be use as the basis for printing the lines of another set of files using awk. What I want to do is something like the one below:
stdev.txt
0.21
0.42
0.32
0.25
0.15
file1.txt file2.txt file3.txt ..filen.txt
0.45 0.23 ... (4 Replies)
Discussion started by: ida1215
4 Replies
LEARN ABOUT REDHAT
man.conf
MAN.CONF(5) File Formats Manual MAN.CONF(5) NAME
man.conf - configuration file for man DESCRIPTION
This is the configuration file for the man(1), apropos(1), and makewhatis(8) utilities. Its presence, and all directives, are optional. This file is an ASCII text file. Leading whitespace on lines, lines starting with '#', and blank lines are ignored. Words are separated by whitespace. The first word on each line is the name of a configuration directive. The following directives are supported: manpath path Override the default search path for man(1), apropos(1), and makewhatis(8). It can be used multiple times to specify multiple paths, with the order determining the manual page search order. Each path is a tree containing subdirectories whose names consist of the strings 'man' and/or 'cat' followed by the names of sections, usually single digits. The former are supposed to contain unformatted manual pages in mdoc(7) and/or man(7) format; file names should end with the name of the section preceded by a dot. The latter should contain preformatted manual pages; file names should end with '.0'. Creating a mandoc.db(5) database with makewhatis(8) in each directory configured with manpath is recommended and necessary for apropos(1) to work, but not strictly required for man(1). output option [value] Configure the default value of an output option. These directives are overridden by the -O command line options of the same names. For details, see the mandoc(1) manual. option value used by -T fragment none html includes string html indent integer ascii, utf8 man string html paper string ps, pdf style string html width integer ascii, utf8 _whatdb path/whatis.db This directive provides the same functionality as manpath, but using a historic and misleading syntax. It is kept for backward compatibility for now, but will eventually be removed. FILES
/etc/man.conf EXAMPLES
The following configuration file reproduces the defaults: installing it is equivalent to not having a man.conf file at all. manpath /usr/share/man manpath /usr/X11R6/man manpath /usr/local/man SEE ALSO
apropos(1), man(1), makewhatis(8) HISTORY
A relatively complicated man.conf file format first appeared in 4.3BSD-Reno. For OpenBSD 5.8, it was redesigned from scratch, aiming for simplicity. AUTHORS
Ingo Schwarze <schwarze@openbsd.org> Debian December 28, 2016 MAN.CONF(5)