Parameter Passing problem Post: 302336839

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

parameter passing

Hallo everyone, This is my problem below: /home/cerebrus/pax=>vat class2.sh ksh: vat: not found /home/cerebrus/pax=>cat class2.sh #!/bin/ksh set -x bdf|grep appsdev|awk '{ print $5 }'> class3 dd={cat class3} echo $dd /home/cerebrus/pax=> /home/cerebrus/pax=>./class2.sh + bdf +...

2. Programming

Passing parameter to makefile?

Hi, How to pass parameter to makefile? Please let me know if any one knows and also please put an example of makefile with this feature. thanks, Manju.

3. Shell Programming and Scripting

wrong parameter passing!

Hi all I have a script which will take input as filename and passes it to a java program. It is as follows -------------------------------- FILENAME=$1 echo $FILENAME ${JAVA_HOME}/bin/java -cp DateProvider $FILENAME ------------------------------------------------- when I execute the same...

4. Shell Programming and Scripting

Passing asterisk As A Parameter

I have written a Shell Script Program which accepts 3 parameters as shown below: ./calc 20 + 2 in the above line ./calc is the Shell Script itself with 3 parameters, namely: 20 + and 2. Well, now let's look inside the Script: result=$1$2$3 echo $result The output will be as...

5. Shell Programming and Scripting

Passing parameter in quotes

Hi, PW='/as sysdba'; export PW in other module I call sqlplus ${PW} (this line I unable to change!) How I can define PW so that sqlplus calls PW in quotes i.e sqlplus '/as sysdba' I tried like this PW="'/as sysdba'"; export PW - no luck Thanks in advance

6. Shell Programming and Scripting

Positional parameter passing

Hi All, When passing parameters to a sheel script, the parameters are referenced by their positions such as $1 for first parameter, $2 for second parameter. these positional values can only have values ranging from $0-$9 (0,1,2,3...9). I have a shell script meant to accept 20 parameters. for...

7. Shell Programming and Scripting

Passing a parameter to AWK

Hi All, I am trying to pass a parameter to AWK on my KSH shell prompt as below. var1=2 echo $var1 awk -v var2=${var1} '{print var2}' testfile.txt I am passing the input file (testfile) to awk to get some o/p. It is having 10 records. When I run AWK, it is throwing the following errors...

8. Programming

passing float parameter

I am surprised by GCC (this is ver. 4.2.4, Ubuntu 32 bit Intel) when a function declares a float parameter and it's prototype is missing, the parameters are messed up. Please see my code below: ~/test$ cat x1.c #include <stdio.h> #include <stdlib.h> set_p(int p1, float p2, int p3, int p4)...

9. Shell Programming and Scripting

Passing parameter to script, and split the parameter

i am passing input parameter 'one_two' to the script , the script output should display the result as below one_1two one_2two one_3two if then echo " Usage : <$0> <DATABASE> " exit 0 else for DB in 1 2 3 do DBname=`$DATABASE | awk -F "_" '{print $1_${DB}_$2}` done fi

10. Shell Programming and Scripting

Passing parameter more than 9

Hi, I've written a script where eleven parameter to be passed from command line which is inserting into an oracle table, it is working but the tenth and 11th parameter are not accepting as given it is referring to 1st parameter. HERE IS THE SCRIPT #!/bin/ksh #set -o echo $*...

LEARN ABOUT FREEBSD

ddb

DDB(8)							    BSD System Manager's Manual 						    DDB(8)

NAME

     ddb -- configure DDB kernel debugger properties

SYNOPSIS

     ddb capture [-M -core] [-N -system] print
     ddb capture [-M -core] [-N -system] status
     ddb script scriptname
     ddb script scriptname=script
     ddb scripts
     ddb unscript scriptname
     ddb pathname

DESCRIPTION

     The ddb utility configures certain aspects of the ddb(4) kernel debugger from user space that are not configured at compile-time or easily
     via sysctl(8) MIB entries.

     To ease configuration, commands can be put in a file which is processed using ddb as shown in the last synopsis line.  An absolute pathname
     must be used.  The file will be read line by line and applied as arguments to the ddb utility.  Whitespace at the beginning of lines will be
     ignored as will lines where the first non-whitespace character is '#'.

OUTPUT CAPTURE

     The ddb utility can be used to extract the contents of the ddb(4) output capture buffer of the current live kernel, or from the crash dump of
     a kernel on disk.	The following debugger commands are available from the command line:

     capture [-M core] [-N system] print
	     Print the current contents of the ddb(4) output capture buffer.

     capture [-M core] [-N system] status
	     Print the current status of the ddb(4) output capture buffer.

SCRIPTING

     The ddb utility can be used to configure aspects of ddb(4) scripting from user space; scripting support is described in more detail in
     ddb(4).  Each of the debugger commands is available from the command line:

     script scriptname
	     Print the script named scriptname.

     script scriptname=script
	     Define a script named scriptname.	As many scripts contain characters interpreted in special ways by the shell, it is advisable to
	     enclose script in quotes.

     scripts
	     List currently defined scripts.

     unscript scriptname
	     Delete the script named scriptname.

EXIT STATUS

     The ddb utility exits 0 on success, and >0 if an error occurs.

EXAMPLES

     The following example defines a script that will execute when the kernel debugger is entered as a result of a break signal:

	   ddb script kdb.enter.break="show pcpu; bt"

     The following example will delete the script:

	   ddb unscript kdb.enter.break

     For further examples, see the ddb(4) and textdump(4) manual pages.

SEE ALSO

     ddb(4), textdump(4), sysctl(8)

HISTORY

     The ddb utility first appeared in FreeBSD 7.1.

AUTHORS

     Robert N M Watson

BUGS

     Ideally, ddb would not exist, as all pertinent aspects of ddb(4) could be configured directly via sysctl(8).

BSD
								 December 24, 2008							       BSD

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting