Sponsored Content
Full Discussion: Passing parameters in script
Top Forums UNIX for Dummies Questions & Answers Passing parameters in script Post 4831 by eliguy on Wednesday 1st of August 2001 01:08:00 PM
Old 08-01-2001
Question Passing parameters in script

I have 2 scripts: script1 and script2

Script1 passes 4 parameters to script2 as follows
#script1
code
...
...
script2 $var1 $var2 $var3 $var4

Script2 uses the export command to know to expect these values
#script2
export $1 $2 $3 $4
code
...
...

The problem that I am having is that some of the values I am passing either have spaces or special characters in them and I get the error (specifically for dates):
script2: 5/7/99: is not an identifier

Any suggestions?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

passing parameters from a shell script to sqlplus

Hi , I want to pass parameters from a shell script to a sql script and use the parameter in the sql query ..and then I want to spool a particular select query on to my unix box... for 4 different locations by writing only one sql script Right now no file is generated on the unix box...it is a... (2 Replies)
Discussion started by: phani
2 Replies

2. Programming

Passing Parameters and getting values back from a c program to Shell script

I am having a shell script which has to be called from a C program. I have to pass two parameters to this script. HOw can I do that? eg: int main() { char st1; char str2; // call a shell script call_sh(str1,str2) where call_sh is the name of the shell script. then i need to get the return... (5 Replies)
Discussion started by: Rajeshsu
5 Replies

3. Shell Programming and Scripting

Random parameters passing in FTP script

Hi I have a question. In the FTP script if we are passing all the required value like Hostname, username, password, Action(put or get), Filename, & mode(ascii or binary) through parameters then we have to pass these in the exact orders in which they are taken like if we defined Username=$2... (2 Replies)
Discussion started by: sourabhshakya
2 Replies

4. Shell Programming and Scripting

Passing parameters to Shell script for GREP command

I am using grep to capture date from a file . Since i need to use the shell script for different dates ,is it possible to pass the date parameter to the shell script the Script is as below grep -E "08 Aug 2008|2008-08-08"* somefile.txt>test.txt The above script file greps the... (1 Reply)
Discussion started by: sud.tech
1 Replies

5. Shell Programming and Scripting

Shell Script Passing Parameters For Directory Listing

i have this basic piece of code that i am trying to debug to accept input parameter to be able to display a directory listing of files. cd /u02/app/eatv/dev/out CURDIR=`pwd` echo directory listing of $CURDIR echo if ; then ls -latr else ls -latr $1 fi basically if the script... (9 Replies)
Discussion started by: wtolentino
9 Replies

6. Shell Programming and Scripting

passing parameters from a script to a datastage job

We have a requirement as follows. We have created a datastage job that will be doing the select operation from table (select query from a table). The datastage job is being invoked by a unix shell script(ksh). We are passing the "table name (STUD_DETAILS)" and a "where clause condition... (4 Replies)
Discussion started by: kmanivan82
4 Replies

7. Shell Programming and Scripting

Passing parameters to bash script function (or subroutine)

I've found a few posts regarding passing parameters to a function or subroutine, but for some reason when I try to run a command based on part with these parameters it's not working. If I have the function echo the parameters they show correctly so I believe they are being passed right but the... (2 Replies)
Discussion started by: withanh
2 Replies

8. Shell Programming and Scripting

passing parameters to the script

how can i make a script to run only when parameters are given, if parameters are not given it should through an error , saying "please enter a parameter" for ex: i want a find command to run only when the parameters are given (4 Replies)
Discussion started by: knip
4 Replies

9. Shell Programming and Scripting

Shell Script passing parameters to sqlplus code

Hello All, I am interested in finding out a way to pass parameters that are entered at the prompt from HP unix and passed to SQLPlus code with a Shell Script. Is this possible? Thanks (4 Replies)
Discussion started by: compprog11
4 Replies

10. Shell Programming and Scripting

Passing command line parameters into script

Not a good post. (1 Reply)
Discussion started by: bash_in_my_head
1 Replies
Net::ManageSieve(3pm)					User Contributed Perl Documentation				     Net::ManageSieve(3pm)

NAME
Net::ManageSieve - ManageSieve Protocol Client SYNOPSIS
use Net::ManageSieve; # Constructors $sieve = Net::ManageSieve->new('localhost'); $sieve = Net::ManageSieve->new('localhost', Timeout => 60); DESCRIPTION
This module implements a client interface to the ManageSieve protocol (<http://tools.ietf.org/html/draft-martin-managesieve-09>). This documentation assumes that you are familiar with the concepts of the protocol. A new Net::ManageSieve object must be created with the new method. Once this has been done, all ManageSieve commands are accessed through this object. Note: ManageSieve allows to manipulate scripts on a host running a ManageSieve service, this module does not perform, validate or something like that Sieve scipts themselves. This module works in taint mode. EXAMPLES
This example prints the capabilities of the server known as mailhost: #!/usr/local/bin/perl -w use Net::ManageSieve; $sieve = Net::ManageSieve->new('mailhost'); print "$k=$v " while ($k, $v) = each %{ $sieve->capabilities }; $sieve->logout; This example lists all storred scripts on the server and requires TLS: #!/usr/local/bin/perl -w use Net::ManageSieve; my $sieve = Net::ManageSieve->new('mailhost', tls => 'require') or die "$@ "; print "Cipher: ", $sieve->get_cipher(), " "; $sieve->login('user', 'password') or die "Login: ".$sieve->error()." "; my $scripts = $sieve->listscripts or die "List: ".$sieve->error()." "; my $activeScript = pop(@$scripts); print "$_ " for sort @$scripts; print $activeScript ? 'active script: ' . $activeScript : 'no script active' , " "; $sieve->logout; ERROR HANDLING
By default all functions return "undef" on failure and set an error description into $@, which can be retrieved with the method "error()" as well. The constructor accepts the setting "on_fail", which alters this behaviour by changing the step to assign $@: If its value is: "warn" the program carps the error description. If "debug" is enabled, too, the description is printed twice. "die" the program croaks. is a CODE ref this subroutine is called with the arguments: &code_ref ( $object, $error_message ) The return value controls, whether or not the error message will be assigned to $@. Private functions may just signal that an error occured, but keep $@ unchanged. In this case $@ remains unchanged, if code_ref returns true. Note: Even if the code ref returns false, $@ might bi clobberred by called modules. This is especially true in the "new()" constructor. otherwise the default behaviour is retained by setting $@. CONSTRUCTOR
new ( [ HOST ] [, OPTIONS ] ) This is the constructor for a new Net::ManageSieve object. "HOST" is the name of the remote host to which an ManageSieve connection is required. "HOST" is optional. If "HOST" is not given then it may instead be passed as the "Host" option described below. If neither is given then "localhost" will be used. "OPTIONS" are passed in a hash like fashion, using key and value pairs. Possible options are: Host - ManageSieve host to connect to. It may be a single scalar, as defined for the "PeerAddr" option in IO::Socket::INET, or a reference to an array with hosts to try in turn. The "host" method will return the value which was used to connect to the host. LocalAddr and LocalPort - These parameters are passed directly to IO::Socket to allow binding the socket to a local port. Timeout - Maximum time, in seconds, to wait for a response from the ManageSieve server (default: 120) Port - Select a port on the remote host to connect to (default is 2000) Debug or debug - enable debugging if true (default OFF) Note: All of the above options are passed through to IO::Socket::INET. tls - issue STARTTLS right after connect. If tls is a HASH ref, the mode is in member "mode", otherwise "tls" itself is the mode and an empty SSL option HASH is passed to starttls(). The "mode" may be one of "require" to fail, if TLS negotiation fails, or "auto", "on" or "yes", if TLS is to attempt, but a failure is ignored. (Aliases: TLS, Tls) on_fail - Changes the error handling of all functions that would otherwise return undef and set $@. See section ERROR HANDLING (Aliases: On_fail) Example: $sieve = Net::ManageSieve->new('mailhost', Timeout => 30, ); use the first host one can connect to successfully "mailhost" on port 2000, the default port, then "localhost" on port 2008. $sieve = Net::ManageSieve->new(Host => [ 'mailhost', 'localhost:2008' ], Timeout => 30, tls => { mode => require, SSL_ca_path => '/usr/ssl/cert', } ); METHODS
Unless otherwise stated all methods return either a true or false value, with true meaning that the operation was a success. When a method states that it returns a value, failure will be returned as undef or an empty list. The error is specified in $@ and can be returned with the "error" method. Please see section ERROR HANDLING for an alternative error handling scheme. close () Closes the connection to the server. Any already cached data is kept active, though, there should be no pending data, if an user calls this function. starttls ( %SSL_opts ) Initiates a TLS session, may be used only before any authentication. The "SSL_opts" is a HASH containing any options you can pass to IO::Socket::SSL->new(). No one is passed by default. In order to detect in the later run, if the connection is encrypted, use the "encrypted()" function. Return: $self or "undef" on failure - the socket is still functioning, but is not encrypted. encrypted () Returns "undef", if the connection is not encrypted, otherwise "true". get_cipher (), dump_peer_certificate (), peer_certificate ($field) Returns "undef", if the connection is not encrypted, otherwise the functions directly calls the equally named function of IO::Socket::SSL. auth (USER [, PASSWORD [, AUTHNAME ] ]) Authentificates as "USER". If the module Authen::SASL is available, this module is tried first. In this case, the "USER" parameter may be a "Authen::SASL" object, that is not furtherly modified. If "USER" is no "Authen::SASL" object, "USER" is passed as "user", "PASSWORD" as "pass" and "AUTHNAME" as "authname" to "Authen::SASL->new()". If "AUTHNAME" is undefined, "USER" is passed as "authname". This way you can authentificate against Cyrus: "auth('cyrus', $password, $username)". If Authen::SASL is not available or the initialization of it fails, this function attempts to authentificate via the "PLAIN" method. Aliases: "login", "authentificate". logout () Sends the "LOGOUT" command to the server and closes the connection to the server. Aliases: "quit", "bye". host () Returns the remote host of the connection. capabilities ([reget]) Returns the capabilities as HASH ref, e.g.: { 'starttls' => 1, 'sasl' => 'PLAIN LOGIN', 'implementation' => 'dovecot', 'sieve' => 'fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex' }; If the argument "bool" is specified and is boolean "TRUE", the capabilities are reaquired from the server using the CAPABILITY command. Note: The initial capabilities may be different from the set acquired later. havespace (NAME, SIZE) Return whether or not a script with the specified size (and name) might fit into the space of the user on the server. Due to various reasons, the result of this function is not very reliable, because in the meantime lots of changes may take place on the server. putscript (NAME, SCRIPT) Stores the "SCRIPT" as name "NAME" on the server, the script is not activated by default. "SCRIPT" is a scalar in UTF-8. The script must not be empty. listscripts () returns an ARRAY ref of the names of the scripts. The last entry in the list, specifies the active script, it is an empty string "", if there is none. e.g.: [ "script1", "script2", "script1" ] means that "script1" is active currently. setactive (NAME) Activates the script named "NAME". getscript (NAME) Returns the named script. The contents is in perl-internal UTF8. deletescript (NAME) Deletes the script named "NAME". error () Returns the locally cached error information in the form: error description respn=last server response debug ( [state] ) Returns the current state of debugging. If "state" is given, the boolean value enables or disables debugging. "str2utf8([encoding,] string)" Encodes the string into internal UTF8. If encoding is specified, it is tried first; then "utf-8-strict", and, if all fails, "Latin1", which is not fail. BUGS
The modules tries hard to pass valid UTF8 data to the server and transforms the results into perl internal UTF8. If latter fails, the transmitted octets are decoded using Latin1. Script names, user names and passwords are not checked or "SASLprep"'ed (RFC 4013/3454). Script names with "[ ]" are rejected. We accept non-synchronizing literals "{num+}" from the server. SEE ALSO
<http://tools.ietf.org/html/draft-martin-managesieve-09> AUTHOR
Steffen Kaiser This module heavily bases on Net::SMTP and Net::Cmd. COPYRIGHT
Copyright (c) 2008-2010 Steffen Kaiser. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2010-07-10 Net::ManageSieve(3pm)
All times are GMT -4. The time now is 06:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy