Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Passing blank arguments to a script
Top Forums UNIX for Advanced & Expert Users Passing blank arguments to a script Post 302156657 by rm-r on Tuesday 8th of January 2008 05:46:12 PM
Old 01-08-2008
Passing blank arguments to a script
All,
I have a cron job script that receives several command line arguments. At some point if there are validation problems and the job cannot be run, it duplicates the entire command line into a temporary text file which is later executed as a script. Unfortunately when I pass the list of received arguments (ie: $*) to this new file, the quoted blank arguments are dismissed.

For example, my script "runbatch.sh" looks like this:
#!/bin/ksh
#runbatch.sh
if [ some validation fails ]
then
echo "$0 $*" >> retryjobs.sh
exit 1
fi

If runbatch.sh was run as:
runbatch.sh one two '' four five

It will convert the 2 single quotes to a blank when exporting the line to retryjobs.sh, thus removing the blank argument.

Here's what retryjobs.sh looks like:
runbatch.sh one two four five

I need those single quotes to be passed. Any ideas anyone??

Thanks
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Passing arguments to a script

I've written a script (bgrep) for a more advanced grep command (& attached a cut down version below). I'm trying allow all grep options to be used, or in any combination. The script works fine if I type say bgrep -i -files product it will return a non-case sensitive list of matches for... (3 Replies)
Discussion started by: Kevin Pryke
3 Replies

2. Shell Programming and Scripting

Passing arguments to a Perl script

I am playing around with Perl and wrote the script below that is executed from the command line, it will split data up in a file based on a value supplied. When executed you provide two arguments - the file that contains the data to be split and the character you want to split by. It works as... (4 Replies)
Discussion started by: jyoung
4 Replies

3. Shell Programming and Scripting

problem passing arguments to script

Hi, I am writing a script, which is invoked from other system using ssh. I have problems reading the arguments passing to the script. If the argument has a space in it (ex "rev 2.00"), the script considers "rev" as 1 argument and "2.00" as another. Instead i want "rev 2.00" to be considered... (5 Replies)
Discussion started by: cjjoy
5 Replies

4. Shell Programming and Scripting

passing arguments to sql script

Hi Gurus, i have one requirement in unix script, i have a file called abc.txt in that few lines are there with the empid, i need to read each line and pass to .sql script. ex: abc.txt 2345 2346 1243 1234 i need to pass these arguments to .sql script rom unix ex: select * from... (1 Reply)
Discussion started by: Devendar
1 Replies

5. Shell Programming and Scripting

passing arguments to external script

Hi! I have a python script that requires arguments and these arguments are file paths. This script works fine when executed like this: /my_python_script "file_path1" "file_path2" (i added quotes as some file names may have weird characters) the issue happens when i launch my python script... (14 Replies)
Discussion started by: gigagigosu
14 Replies

6. Shell Programming and Scripting

Passing arguments to a perl script

Hi I need to pass comma seperated arguments to a perl script? It is like: Exect.pl -d GUI1,GUI2,GUI3 and I need to store these argsGUI1,GUI2,GUI3 in an array. can anyone suggest how to do that: (1 Reply)
Discussion started by: rkrish
1 Replies

7. Shell Programming and Scripting

Passing multiple arguments to a shell script

Hi Gurus, Need some help with the shell scripting here. #!/bin/ksh ps -ef | grep -i sample.ksh | grep -v grep > abc.txt if then echo "sample.ksh is executing" else echo "sample.ksh is not executing" fi (1 Reply)
Discussion started by: jayadanabalan
1 Replies

8. Shell Programming and Scripting

Passing arguments to a bash script

Hi, I wanted to pass an argument to a bash script. So that the argument is used inside the awk command inside the bash script. I know the noraml way of passing argument to a bash script as below : sh myScript.sh abc Inside the bash script i can use like this myArg1=$1 wc $myArg But... (8 Replies)
Discussion started by: shree11
8 Replies

9. Shell Programming and Scripting

Passing arguments while running the script

Hi, I have a requirement for creating a MQ (queue) where the inputs has to be passed as arguments. Running the script as below ./hi.sh "Servername" "QueueManagername" "QueuecreationCommand" cat hi.sh echo "Welcome to $1" runmqsc $2 < $3 But the queue creation command is... (9 Replies)
Discussion started by: Anusha M
9 Replies

10. Shell Programming and Scripting

Passing arguments to php script

i want to be able to pass arguments to a php script if it is being piped: cat myphpscript.php | php - $1 $2 $3 blah blah This usually works for other script languages...i.e. ruby: cat myrubyscript.rb | ruby - $1 $2 $3 blah blah so my question is, how can i pass arguments to my php... (1 Reply)
Discussion started by: SkySmart
1 Replies

LEARN ABOUT CENTOS

anacrontab

ANACRONTAB(5)							   File Formats 						     ANACRONTAB(5)

NAME

       /etc/anacrontab - configuration file for Anacron

DESCRIPTION

       The  /etc/anacrontab  configuration file describes the jobs controlled by anacron(8).  It can contain three types of lines: job-description
       lines, environment assignments, or empty lines.

       Job-description lines can have the following format:

	  period in days   delay in minutes   job-identifier   command

       The period in days variable specifies the frequency of execution of a job in days.  This variable can be represented by	an  integer  or  a
       macro (@daily, @weekly, @monthly), where @daily denotes the same value as the integer 1, @weekly the same as 7, and @monthly specifies that
       the job is run once a month, independent on the length of the month.

       The delay in minutes variable specifies the number of minutes anacron waits, if necessary, before executing a job.  This variable is repre-
       sented by an integer where 0 means no delay.

       The job-identifier variable specifies a unique name of a job which is used in the log files.

       The  command  variable specifies the command to execute.  The command can either be a command such as ls /proc >> /tmp/proc or a command to
       execute a custom script.

       Environment assignment lines can have the following format:

	  VAR=VALUE

       Any spaces around VAR are removed.  No spaces around VALUE are allowed (unless you want them to be  part  of  the  value).   The  specified
       assignment takes effect from the next line until the end of the file, or to the next assignment of the same variable.

       The  START_HOURS_RANGE  variable  defines an interval (in hours) when scheduled jobs can be run.  In case this time interval is missed, for
       example, due to a power down, then scheduled jobs are not executed that day.

       The RANDOM_DELAY variable denotes the maximum number of minutes that will be added to the delay in minutes variable which is specified  for
       each  job.   A  RANDOM_DELAY set to 12 would therefore add, randomly, between 0 and 12 minutes to the delay in minutes for each job in that
       particular anacrontab.  When set to 0, no random delay is added.

       Empty lines are either blank lines, line containing white spaces only, or lines with white spaces followed by a '#' followed  by  an  arbi-
       trary comment.

       You can continue a line onto the next line by adding a '' at the end of it.

       In  case  you want to disable Anacron, add the 0anacron cron job (which is a part of crontab(1)) into the /etc/cron.hourly/jobs.deny direc-
       tory.

EXAMPLE

       This example shows how to set up an Anacron job similar in functionality to /etc/crontab which starts all regular  jobs	between  6:00  and
       8:00 only.  A RANDOM_DELAY which can be 30 minutes at the most is specified.  Jobs will run serialized in a queue where each job is started
       only after the previous one is finished.

       # environment variables
       SHELL=/bin/sh
       PATH=/sbin:/bin:/usr/sbin:/usr/bin
       MAILTO=root
       RANDOM_DELAY=30
       # Anacron jobs will start between 6am and 8am.
       START_HOURS_RANGE=6-8
       # delay will be 5 minutes + RANDOM_DELAY for cron.daily
       1	 5    cron.daily	  nice run-parts /etc/cron.daily
       7	 0    cron.weekly	  nice run-parts /etc/cron.weekly
       @monthly  0    cron.monthly	  nice run-parts /etc/cron.monthly

SEE ALSO

       anacron(8), crontab(1)

       The Anacron README file.

AUTHOR

       Itai Tzur <itzur@actcom.co.il>

       Currently maintained by Pascal Hakim <pasc@(debian.org|redellipse.net)>.

       For Fedora, maintained by Marcela Malaova <mmaslano@redhat.com>.

cronie								    2012-11-22							     ANACRONTAB(5)
All times are GMT -4. The time now is 02:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy