Why "$TBS" ? If TBS is empty, you get error if not "". Usually it's safety to use always " " with variable. String length 0 / null string.
This is one of the few instances where it is never necessary to quote the variable; case is a shell keyword, not a builtin command, so it doesn't parse the line as if it were a command.
Even if $TBS could be empty, there's no need to quote it.
Hi! I'm using
echo $string | grep "" -c
to test in a script if a string is a number and it seems to work. But how can i find, for example, if a string is a four figures number ?
Thanks to all! (2 Replies)
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)
This is the code:
while test 1 -eq 1
do
read a
$a
if test $a = stop
then
break
fi
done
I read a command on every loop an execute it.
I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test.
For example echo hello.
Now the... (1 Reply)
Hello all,
I'm trying to automate an if statement in my Perl script. The script opens an input file for reading, checks each line in the file for a particular substring, and if it finds the substring, writes it to an output file.
There are approximately 200 different input files. Each has... (3 Replies)
Hello,
I am trying to build a test statement but I can't make it work
I want to rearrange some fields, so if my "$cfg" variable contains a string ending with .log (*.log) I want to move it in another field.
Any help will be much appreciated!
Thank you
Shell:sh
if
then
log="${cfg}"... (9 Replies)
Is it possible to test against a varible within a ranges in a if statement.
ex.
if ];then
echo "not in range"
else
echo "number within range"
fi (8 Replies)
Discussion started by: leemalloy
8 Replies
LEARN ABOUT ULTRIX
xlator_call
xlator_call(8) System Manager's Manual xlator_call(8)Name
xlator_call - shell script to invoke PostScript translators
Syntax
xlator_call datatype orientation pagesize width length indent
Description
This Bourne shell script can be called by the line printer daemon to invoke the appropriate translator to convert each data type to Post-
Script. The data type passed by may be specified by using the command with the -Ddatatype option, or by using the Da=datatype capability
in the file.
For a file in a data syntax to be translated to PostScript, the script must contain a case branch which recognizes the data type string and
calls a suitable filter. The supplied recognizes the ANSI, ASCII, ReGIS and Tektronix 4014 data types.
Arguments
datatype
The valid data types are: or any other for which a translator has been installed.
orientation
The valid orientations are: portrait or landscape.
pagesize
The valid page sizes are: or
width
The width (in characters) of the page.
length
The length (in lines) of the page.
indent
The amount (in spaces) the output is to be indented.
All the valid arguments are described in detail by the reference page.
Examples
An example shell script is shown below:
case $datatype in
ansi)
exec ansi_ps -F $pagesize -O $orientation -e "$@";;
ascii)
echo "( 04) cvn {} def"
exec ln03rof -w$width -l$length -i$indent;;
postscript)
exec cat;;
tek4014)
exec tek4014_ps -F $pagesize -O $orientation;;
regis)
exec regis_ps -F $pagesize -O $orientation;;
*)
echo "$0: Translator for data type $datatype not installed" >&2
esac
When the shell script is called, the path searched is:
/usr/local/lib/lpdfilters:/usr/ucb:/bin:/usr/bin:
/usr/lib:/usr/lib/lpdfilters
Files
The script
See Alsolno3rof(8), printcap(5), ansi_ps(8), lpd(8)xlator_call(8)