Thanks... that ought to be enough to let me figure it out. FWIW, the original code looked like this, and it works. (Which are certainly not to say that it couldn't be cleaner -- I'm only just starting with bash scripting.)
Hi,
I have a shell script Scp_1.sh for which I have to pass 2 arguments to run.
I have another script Scp_2.sh which in turns calls script Scp_1.sh inside.
How do I make Scp_1.sh script to read arguments automatically from a file, while running Scp_2.sh?
--
Weblogic Support (4 Replies)
hi I am new to shell programming.....my question is while running one of my shell program it stops in between to accept input from the user and proceeds furthur after giving input....I want to know whether I can set this input through some files so that the shell acript reads the input from the... (10 Replies)
Hi, hope everyone are fine. Please find my issue below, and I request your help in the same
In a configuration file, i have a variable defined as below
TEST = 'One','Two','Three'
I am trying to pass this variable in to a sql script which is define in a pl/sql block
as follows,
In the... (1 Reply)
hi everobody
kindly consider the following
in tclsh
I understand that we can do the following
%exec UnixCmd arg1 arg2
but if I assinged the arguments to a list insde tclsh how can I use them back
i.e
%set ArgList
%exec UnixCmd
%exec Unixcmd $list
%exec
all the... (1 Reply)
Hello
Please i want to pass parameter (the string s) to the shell script:
Quote:
String s="Hello";
Process process = Runtime.getRuntime().exec("sh script1.sh");
How can i do please?
Thank you (0 Replies)
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)
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)
Dear Users,
I have installed a standalone program to do multiple sequence alignment which takes user parameters to run the program. I have multiple sequence files and want to automate this process through a bash script. I have tried to write a small bash code but its throwing errors.
Kindly... (13 Replies)
I found something insteresting when I tested passing arguments into my scripts.
My scripts is as below.
% cat passarg.env
#!/bin/csh
echo "passarg: argv = $argv argv = $argv"
passarg1.env $*
% cat passarg1.env
#!/bin/csh
echo "passarg1: argv = $argv argvp=$argv"
set str = "test... (5 Replies)
Hi All,
I have below simple shell script in cloudera quick start vm cenos 6 which copy file from source to destination.
# file_copy.sh
source_dir = ${source_dir}
target = ${target_dir}
cp source_dir target
and my parameter file is like below
#parameter_file.txt
source_dir =... (4 Replies)
Discussion started by: Narasimhasss
4 Replies
LEARN ABOUT LINUX
pod2latex
POD2LATEX(1) Perl Programmers Reference Guide POD2LATEX(1)NAME
pod2latex - convert pod documentation to latex format
SYNOPSIS
pod2latex *.pm
pod2latex -out mytex.tex *.pod
pod2latex -full -sections 'DESCRIPTION|NAME' SomeDir
pod2latex -prefile h.tex -postfile t.tex my.pod
DESCRIPTION
"pod2latex" is a program to convert POD format documentation (perlpod) into latex. It can process multiple input documents at a time and
either generate a latex file per input document or a single combined output file.
OPTIONS AND ARGUMENTS
This section describes the supported command line options. Minimum matching is supported.
-out
Name of the output file to be used. If there are multiple input pods it is assumed that the intention is to write all translated output
into a single file. ".tex" is appended if not present. If the argument is not supplied, a single document will be created for each
input file.
-full
Creates a complete "latex" file that can be processed immediately (unless "=for/=begin" directives are used that rely on extra
packages). Table of contents and index generation commands are included in the wrapper "latex" code.
-sections
Specify pod sections to include (or remove if negated) in the translation. See "SECTION SPECIFICATIONS" in Pod::Select for the format
to use for section-spec. This option may be given multiple times on the command line.This is identical to the similar option in the
"podselect()" command.
-modify
This option causes the output "latex" to be slightly modified from the input pod such that when a "=head1 NAME" is encountered a
section is created containing the actual pod name (rather than NAME) and all subsequent "=head1" directives are treated as subsections.
This has the advantage that the description of a module will be in its own section which is helpful for including module descriptions
in documentation. Also forces "latex" label and index entries to be prefixed by the name of the module.
-h1level
Specifies the "latex" section that is equivalent to a "H1" pod directive. This is an integer between 0 and 5 with 0 equivalent to a
"latex" chapter, 1 equivalent to a "latex" section etc. The default is 1 ("H1" equivalent to a latex section).
-help
Print a brief help message and exit.
-man
Print the manual page and exit.
-verbose
Print information messages as each document is processed.
-preamble
A user-supplied preamble for the LaTeX code. Multiple values are supported and appended in order separated by "
". See -prefile for
reading the preamble from a file.
-postamble
A user supplied postamble for the LaTeX code. Multiple values are supported and appended in order separated by "
". See -postfile for
reading the postamble from a file.
-prefile
A user-supplied preamble for the LaTeX code to be read from the named file. Multiple values are supported and appended in order. See
-preamble.
-postfile
A user-supplied postamble for the LaTeX code to be read from the named file. Multiple values are supported and appended in order. See
-postamble.
BUGS
Known bugs are:
o Cross references between documents are not resolved when multiple pod documents are converted into a single output "latex" file.
o Functions and variables are not automatically recognized and they will therefore not be marked up in any special way unless instructed
by an explicit pod command.
SEE ALSO
Pod::LaTeX
AUTHOR
Tim Jenness <tjenness@cpan.org>
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
Copyright (C) 2000, 2003, 2004 Tim Jenness. All Rights Reserved.
perl v5.12.4 2013-03-18 POD2LATEX(1)