Sponsored Content
Full Discussion: test: argument expected
Top Forums Shell Programming and Scripting test: argument expected Post 302166284 by lalelle on Monday 11th of February 2008 01:26:57 PM
Old 02-11-2008
test: argument expected

+ [ -e /etc/passwd ]
test.sh: test: argument expected

#!/bin/bash
if [ -e /etc/passwd ]
then
echo thennnn
else
echo elseeee
fi

why does it show this error? Clearly from debug mode, the argument is passed. I also tried if [ -e "/etc/passwd" ]


Run on Solaris 9.
Thanks
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

ERROR-> test: argument expected , what does it mean?

I am trying to compare two integer variables in the if statement, but i am getting this "test:argument expected". What am i missing? Why is the if loop not executing correctly? trunkPCM="100000"; more $FILE |while read line do PCM=`echo $line | awk '{ print $2 }'` ... (4 Replies)
Discussion started by: tan102938
4 Replies

2. UNIX for Dummies Questions & Answers

test:argument expected

Hi all, I am getting "test:argument expected" error in the following script LOGDIR=$XXAR_TOP/log PROGRAM_NAME=XXAR_GPS_LBFDMSGEN .. .. .. Check_Errors() { sqllogfile=$1 cd ${LOGDIR} countfile=${LOGDIR}/${PROGRAM_NAME}.tmp echo "countfile is " $countfile >> $LOGFILE echo... (4 Replies)
Discussion started by: rrs
4 Replies

3. Shell Programming and Scripting

test: argument expected

Can someone help me with a very simple query I have the following script: #!/bin/sh VAR1="" if then VAR1="Message" fi echo $VAR1 put when i run it i get the following error test_job.sh: test: argument expected (5 Replies)
Discussion started by: andy202
5 Replies

4. Shell Programming and Scripting

test: argument expected

I'm newbie to coding script so i found test: argument expected when i run it. please help me a=`df -k |awk '{print $5 }'|egrep "(100%|%)"|cut -d"%" -f1|tail -1` if then df -k|egrep "(100%|%)"|awk '{print $1,$5,$6}' else echo "No disk capacity more than 80%" fi thk in advance (7 Replies)
Discussion started by: unitipon
7 Replies

5. Shell Programming and Scripting

Test: argument expected.

Hi, Since i am new to Unix and on suggestion on some smart guys on unix... i have decide to learn more deeply on Unix...so i was kind of playing with if statements and found this error... though i tried to correct is for hours now i couldnt find whats wrong in my loop. if then ... (4 Replies)
Discussion started by: bhagya2340
4 Replies

6. Shell Programming and Scripting

test: argument expected

# to search a file if it exists and whether its readable or not # if yes print its first 5 lines echo enter the filename to be searched read fname if #-d $fname then echo file doesn exists elif then echo its a directory elif then cat $fname else echo its not readable fi # end of... (9 Replies)
Discussion started by: gotam
9 Replies

7. Shell Programming and Scripting

error : test: argument expected

Hello all, I am trying to figure out why i am getting an error while executing the script...altought it seems like its work...but still get the test arguement error...any help would be appericiate...this script basically connects to any oracle db ( just have to pass db name to it)... (4 Replies)
Discussion started by: abdul.irfan2
4 Replies

8. UNIX for Advanced & Expert Users

Error:--test: argument expected--Even though i give an argument.

Hi All, I am running the script VBoxManage list vms |sed 's/"//g' | cut -d " " -f1 > har1out.mytxt result=`cat har1out.mytxt | grep $1' echo $result echo $1 { if then echo pass else echo fail fi (2 Replies)
Discussion started by: harsha85
2 Replies

9. Shell Programming and Scripting

Error- test: argument expected

check_build_info_table() { if then export build_info_table=`sqlplus -s sna/dbmanager <<! set pagesize 0 heading off feedback off SELECT DISTINCT TABLE_NAME FROM ALL_TABLES WHERE OWNER = 'XYZ' AND TABLE_NAME = 'MY_TABLE'; exit !` ... (3 Replies)
Discussion started by: ambarginni
3 Replies

10. Shell Programming and Scripting

Test: argument expected

The following example prompts are passed into the shell script. $1 = /tmp/dir/ $2 = varies (test.txt, test1.txt, test2.txt...) $3 = test_YYYYMMDD.txt --------------------------------------------------------------------------- #!/bin/sh cd $1 if ; then if ; then ... (3 Replies)
Discussion started by: smkremer
3 Replies
PEGASUS-INVOKE(1)														 PEGASUS-INVOKE(1)

NAME
pegasus-invoke - invokes a command from a file SYNOPSIS
pegasus-invoke ( app | @fn ) [ arg | *@fn [..]] DESCRIPTION
The pegasus-invoke tool invokes a single application with as many arguments as your Unix permits (128k characters for Linux). Arguments are come from two places, either the command-line as regular arguments, or from a special file, which contains one argument per line. The pegasus-invoke tool became necessary to work around the 4k argument length limit in Condor. It also permits to use arguments inside argument files without worry about shell, Condor or Globus escape necessities. All argument file contents are passed as is, one line per argument entry. ARGUMENTS
-d This option increases the debug level. Currently, only debugging or no debugging is distinguished. Debug message are generated on stdout . By default, debugging is disabled. -h This option prints the help message and exits the program. -- This option stops any option processing. It may only be necessary, if the application is stated on the command-line, and starts with a hyphen itself.The first argument must either be the application to run as fully-specified location (either absolute, or relative to current wd), or a file containing one argument per line. The PATH environment variables is not used to locate an application. Subsequent arguments may either be specified explicitely on the commandline. Any argument that starts with an at (@) sign is taken to introduce a filename, which contains one argument per line. The textual file may contain long arguments and filenames. However, Unices still impose limits on the maximum length of a directory name, and the maximum length of a file name. These lengths are not checked, because pegasus-invoke is oblivious of the application (e.g. what argument is a filename, and what argument is a mere string resembling a filename). RETURN VALUE
The pegasus-invoke tool returns 127, if it was unable to find the application. It returns 126, if there was a problem parsing the file. All other exit status, including 126 and 127, come from the application. SEE ALSO
pegasus-kickstart(1) EXAMPLE
$ echo "/bin/date" > X $ echo "-Isec" >> X $ pegasus-invoke @X 2005-11-03T15:07:01-0600 Recursion is also possible. Please mind not to use circular inclusions. Also note how duplicating the initial at (@) sign will escape its meaning as inclusion symbol. $ cat test.3 This is test 3 $ cat test.2 /bin/echo @test.3 @@test.3 $ pegasus-invoke @test.2 This is test 3 @test.3 RESTRICTIONS
While the arguments themselves may contain files with arguments to parse, starting with an at (@) sign as before, the maximum recursion limit is 32 levels of inclusions. It is not possible (yet) to use stdin as source of inclusion. HISTORY
As you may have noticed, pegasus-invoke had the name invoke in previous incantations. We are slowly moving to the new name to avoid clashes in a larger OS installation setting. However, there is no pertinent need to change the internal name, too, as no name clashes are expected. AUTHORS
Mike Wilde <wilde at mcs dot anl dot gov> Jens-S. Vockler <voeckler at isi dot edu> Pegasus http://pegasus.isi.edu/ 05/24/2012 PEGASUS-INVOKE(1)
All times are GMT -4. The time now is 03:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy