Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: getopts problem
Top Forums UNIX for Advanced & Expert Users getopts problem Post 302257401 by mobydick on Wednesday 12th of November 2008 04:34:12 AM
Old 11-12-2008
getopts issue
in the below script i am expecting the variable surname to be changed but that is not happening can anyone help and explain why and how to do that


surname=halder

echo $surname

while getopts "Smilie" OPTION
do
case $OPTION in

b) surname=bose
;;

esac
done

echo $surname
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

getopts

I have a script that facillitates NDM (Connect::\Direct) transfer to remote hosts. This script uses getopts to parse through the parameters passed to it and to set appropriate variables based upon what was passed in. Kickoff="mv $PATH/$FILE1 $PATH/$FILE2" ndm_shell.ksh -p $Node -s $Source -d... (3 Replies)
Discussion started by: google
3 Replies

2. Shell Programming and Scripting

Problem with getopts

I need to parse parameters but the arguments could be NULL,example: > cat getopts.sh while getopts "a:b:" opt 2>/dev/null do case "${opt}" in a) echo "A:${OPTARG}" ;; b) echo "B:${OPTARG}" ;; *) exit 1 ;; esac done > getopts.sh -a TEST1 -b TEST2... (5 Replies)
Discussion started by: Klashxx
5 Replies

3. Shell Programming and Scripting

getopts help

Hi i have part of the scripts below ,getopt for -h or ? not working for me. can anybody tell me if this sytax right or wrong. #!/usr/bin/ksh program=$(basename $0) ##################################################################################### function usageerr { RC=1 ... (3 Replies)
Discussion started by: GrepMe
3 Replies

4. Shell Programming and Scripting

Problem in getopts

while getopts l:f:s:o:h: c do case $c in l) tail -${OPTARG} /etc/passwd exit 2;; f) head -${OPTARG} /etc/passwd exit 3;; s) grep ${OPTARG} /etc/passwd | cut -d: -f7 exit 4;; o) OARG=$OPTARG exit 5;; h) ... (3 Replies)
Discussion started by: nadman123
3 Replies

5. Shell Programming and Scripting

problem with getopts

Hi, I am a new member to unix.com. Actually I am facing a problem with getopts. In my script i have used getopts to parse the parameters. when i use the script as shown below its working fine: find_status -p all ### where find_status is a script name. But even if I pass more than one... (3 Replies)
Discussion started by: pvamsikr
3 Replies

6. Shell Programming and Scripting

getopts problem

How do I get the getopts command to display whats written at my help option if no option is types in? For example, myscript.sh -h will bring up my help option, however, I also want myscript.sh to do the same! #!/bin/bash while getopts :abh opt do case "$opt" in... (2 Replies)
Discussion started by: linuxkid
2 Replies

7. Shell Programming and Scripting

getopts problem

Hi everyone I want to know how can we pass multiple argument in getopts suppose PARAMS="abcd" while getopts ${PARMS} FLAG do case ${FLAG} in (a) (b) (c) (d) esac (6 Replies)
Discussion started by: aishsimplesweet
6 Replies

8. Shell Programming and Scripting

getopts - optional and problem to display help

In the below code while getopts :rfw:d:s:a: options do case "$options" in r) echo reverse;; f) echo forward;; w) window=$OPTARG;; d) duration=$OPTARG;; s) search=$OPTARG;; a) value=$OPTARG;; *) help; exit;; esac done ... (2 Replies)
Discussion started by: Amutha
2 Replies

9. Shell Programming and Scripting

problem with getopts

Hi, I have written a script to take command line arguments using geopts.This is the code. #!/bin/sh # The usage of this script. usage="Usage is $0" usage="$usage " usage="$usage " usage="$usage " # Use the getopt utility to set up the command line flags. set -- `/usr/bin/getopt... (4 Replies)
Discussion started by: arijitsaha
4 Replies

10. Shell Programming and Scripting

Identify problem with while getopts

can anyone spot a problem with the below: $ $ cat getopts.sh #!/bin/sh usage() { echo "myscript.sh local /tmp data.txt 600s -query" 1>&2; exit 1; } while... (4 Replies)
Discussion started by: SkySmart
4 Replies

LEARN ABOUT DEBIAN

cgi::xmlform

XMLForm(3pm)						User Contributed Perl Documentation					      XMLForm(3pm)

NAME

       CGI::XMLForm - Extension of CGI.pm which reads/generates formated XML.

       NB: This is a subclass of CGI.pm, so can be used in it's place.

SYNOPSIS

	 use CGI::XMLForm;

	 my $cgi = new CGI::XMLForm;

	 if ($cgi->param) {
	       print $cgi->header, $cgi->pre($cgi->escapeHTML($cgi->toXML));
	 }
	 else {
	       open(FILE, "test.xml") or die "Can't open: $!";
	       my @queries = ('/a', '/a/b*', '/a/b/c*', /a/d');
	   print $cgi->header,
		     $cgi->pre($cgi->escapeHTML(
			 join "
", $cgi->readXML(*FILE, @queries)));
	 }

DESCRIPTION

       This module can either create form field values from XML based on XQL/XSL style queries (full XQL is _not_ supported - this module is
       designed for speed), or it can create XML from form values. There are 2 key functions: toXML and readXML.

       toXML

       The module takes form fields given in a specialised format, and outputs them to XML based on that format. The idea is that you can create
       forms that define the resulting XML at the back end.

       The format for the form elements is:

	 <input name="/body/p/ul/li">

       which creates the following XML:

	 <body>
	   <p>
		 <ul>
		   <li>Entered Value</li>
		 </ul>
	       </p>
	 </body>

       It's the user's responsibility to design appropriate forms to make use of this module. Details of how come below...

       Also supported are attribute form items, that allow creation of element attributes. The syntax for this is:

	 <input name="/body/p[@id='mypara' and @onClick='someFunc()']/@class">

       Which creates the following XML:

	 <body>
	   <p id="mypara" onClick="someFunc()" class="Entered Value"></p>
	 </body>

       Also possible are relative paths. So the following form elements:

	 <input type="hidden" name="/table/tr">
	 <input type="text" name="td">
	 <input type="text" name="td">
	 <input type="text" name="../tr/td">

       Will create the following XML:

	 <table>
	   <tr>
		 <td>value1</td>
		 <td>value2</td>
	       </tr>
	       <tr>
		 <td>value3</td>
	       </tr>
	 </table>

SYNTAX

       The following is a brief syntax guideline

       Full paths start with a "/" :

	 "/table/tr/td"

       Relative paths start with either ".." or just a tag name.

	 "../tr/td"
	 "td"

       Relative paths go at the level above the previous path, unless the previous path was also a relative path, in which case it goes at the
       same level. This seems confusing at first (you might expect it to always go at the level above the previous element), but it makes your
       form easier to design. Take the following example: You have a timesheet (see the example supplied in the archive) that has monday,tues-
       day,etc. Our form can look like this:

	 <input type="text" name="/timesheet/projects/project/@Name">
	 <input type="text" name="monday">
	 <input type="text" name="tuesday">
	 ...

       Rather than:

	 <input type="text" name="/timesheet/projects/project/@Name">
	 <input type="text" name="monday">
	 <input type="text" name="../tuesday">
	 <input type="text" name="../wednesday">
	 ...

       If unsure I recommend using full paths, relative paths are great for repeating groups of data, but weak for heavily structured data. Pic-
       ture the following paths:

	 /timesheet/employee/name/forename
	 ../surname
	 title
	 ../department

       This actually creates the following XML:

	 <timesheet>
	   <employee>
		 <name>
		   <forename>val1</forname>
		       <surname>val2</surname>
		       <title>val3></title>
		 </name>
		 <department>val4</department>
	       </employee>
	 </timesheet>

       Confusing eh? Far better to say:

	 /timesheet/employee/name/forename
	 /timesheet/employee/name/surname
	 /timesheet/employee/name/title
	 /timesheet/employee/department

       Or alternatively, better still:

	 /timesheet/employee/name (Make hidden and no value)
	 forename
	 surname
	 title
	 ../department

       Attributes go in square brackets. Attribute names are preceded with an "@", and attribute values follow an "=" sign and are enclosed in
       quotes. Multiple attributes are separated with " and ".

	 /table[@bgcolor="blue" and @width="100%"]/tr/td

       If setting an attribute, it follows after the tag that it is associated with, after a "/" and it's name is preceded with an "@".

	 /table/@bgcolor

       readXML

       readXML takes either a file handle or text as the first parameter and a list of queries following that. The XML is searched for the queries
       and it returns a list of tuples that are the query and the match.

       It's easier to demonstrate this with an example. Given the following XML:

	 <a>Foo
	   <b>Bar
		 <c>Fred</c>
		 <c>Blogs</c>
	       </b>
	       <b>Red
		 <c>Barbara</c>
		 <c>Cartland</c>
	       </b>
	       <d>Food</d>
	 </a>

       And the following queries:

	 /a
	 /a/b*
	 c*
	 /a/d

       it returns the following result as a list:

	 /a
	 Foo
	 /a/b
	 Bar
	 c
	 Fred
	 c
	 Blogs
	 /a/b
	 Red
	 c
	 Barbara
	 c
	 Cartland
	 /a/d
	 Food

       (NB: This is slightly incorrect - for /a and /a/b it will return "Foo
    " and "Bar
      " respectively).

       The queries support relative paths like toXML (including parent paths), and they also support wildcards using ".*" or ".*?" (preferably
       ".*?" as it's probably a better match). If a wildcard is specified the results will have the actual value substituted with the wildcard.
       Wildcards are a bit experimental, so be careful ;-)

       Caveats

       There are a few caveats to using this module:

AUTHOR

	   Matt Sergeant msergeant@ndirect.co.uk, sergeant@geocities.com

	   Based on an original concept, and discussions with, Jonathan Eisenzopf.  Thanks to the Perl-XML mailing list for suggesting the XSL
	   syntax.

	   Special thanks to Francois Belanger (francois@sitepak.com) for his mentoring and help with the syntax design.

SEE ALSO

       CGI(1), CGI::XML

perl v5.8.8							    2005-01-18							      XMLForm(3pm)
All times are GMT -4. The time now is 11:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy