08-24-2009
One way I've seen it done is to save the parameters in variables, export them, then immediately exec a different script. The new script will obtain values through environment variables and not display them in its commandline, while the program that called it no longer exists, having been replaced with whatever it exec'd. This makes it difficult -- though not impossible -- to catch in the act.
Another way to avoid parameters being visible is to not have them visible in the first place, transferring them to scripts through methods like pipes and so forth.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
All,
I have a sh script of the following tune:
function a () { #functionality.. }
function b () { #functionnlity.. }
function check () { # this function checks for env and if all fine call build }
function usage () { #sh usage details }
function build () { #calls either a or b or... (5 Replies)
Discussion started by: vino
5 Replies
2. UNIX for Dummies Questions & Answers
I need to take in two parameters from the command line...help! (1 Reply)
Discussion started by: avisram
1 Replies
3. Shell Programming and Scripting
I couldn't find an existing thread that addressed this question, so hopefully this isn't redundant with anything previously posted. Here goes:
I am writing a C-Shell script that runs a program that takes an arbitrary number of parameters:
myprog -a file1 \
-b file2 \
-c file3 ... \
-n... (2 Replies)
Discussion started by: cmcnorgan
2 Replies
4. UNIX for Dummies Questions & Answers
Iam running a report(.rdf) file from UNIX command line.
using the following syntax
for eg xxx.rdf is the report rdf
ar60run batch=yes userid=username/paswd@database report=xxx.rdf destype=file desname=xxx.dat
now i need to submit this with three pameters
pls suggest (1 Reply)
Discussion started by: sreenusola
1 Replies
5. UNIX for Advanced & Expert Users
I am running Putty 0.60 from Windows XP and I am connecting to a Linux box.
I would like to be able to pass a command line parameter to my Linux session so that my Linux session can execute a specific command, depending on the command line parameter. I have looked on the Internet and tried... (1 Reply)
Discussion started by: SFNYC
1 Replies
6. UNIX for Dummies Questions & Answers
hi,
This is actually realted to a Abinitio command in a unix script. my code is
#!/bin/ksh
GRAPH_NAME=$1
shift
air sandbox run $GRAPH_NAME $* > file.lst 2>&1
if ]; then echo "Pass"
fi
when i run this script with this command "script.ksh graph_name parameters"
the script... (1 Reply)
Discussion started by: siva1612
1 Replies
7. UNIX for Dummies Questions & Answers
hi again
question on how to change code so that script will prompt to enter parameter if they are missing. . .
code I have so far :
#!/bin/bash
two="200"
three=500
if ; then
echo " first line parameter is $one "
else
echo -n " first parameter is missing , please write... (2 Replies)
Discussion started by: me.
2 Replies
8. Shell Programming and Scripting
Hi,
I have a script which has 3 command line parameters.But sometimes it will also take 2 command line parameters or 1.How to do it?
I am using $1,$2... to specify the command line parameters.
The script which i have written is given below.
#!/bin/sh
echo "database="$1
echo... (3 Replies)
Discussion started by: arijitsaha
3 Replies
9. Programming
Hi,
I need to somehow pipe the password to a command and run some SQL, for example, something like echo $password | sqlplus -s system @query01.sql
To make it not so obvious, I decided to try out writing a small C program that basically just do echo $password. So now I just do x9.out | sqlplus... (8 Replies)
Discussion started by: newbie_01
8 Replies
10. Shell Programming and Scripting
Not a good post. (1 Reply)
Discussion started by: bash_in_my_head
1 Replies
LEARN ABOUT DEBIAN
dh-exec
DH-EXEC(1) dh-exec DH-EXEC(1)
NAME
dh-exec - Debhelper executable file helpers
SYNOPSIS
#! /usr/bin/dh-exec
src/libfoo-*.so.* debian/foo-plugins/usr/lib/foo/${DEB_HOST_MULTIARCH}/
etc/example.conf => debian/foo/etc/foo/foo.conf
DESCRIPTION
dh-exec is a simple program, meant to be used as the interpreter for executable debhelper config files.
It is a wrapper around the various other sub-commands (see below), and will pipe the input file through all of them in turn, using an
ordering that makes most sense in the vast majority of cases.
The order as of now is dh-exec-subst gets run first, followed by dh-exec-install, so that variable expansion happens before files need to
be copied.
ARCHITECTURE
dh-exec is built up from three layers: there is the dh-exec utility, its single entry point, the only thing one will need to call.
Below that, there are the various sub-commands, such as dh-exec-subst, dh-exec-installs and dh-exec-illiterate, which are thin wrappers
around the various dh-exec scripts, that make sure they only run those that need to be run.
And the lowest layer are the various scripts that do the actual work.
One can control which sub-commands to run, or if even more granularity is desired, one can limit which scripts shall be run, too. See below
for the options!
OPTIONS
--with=command[,command ...]
Replace the list of sub-commands to run the input through with a custom list (where entries are separated by whitespace or commas).
This option will always replace the existing list with whatever is specified.
This can be used to explicitly set which sub-commands to use.
The list must not include the dh-exec- prefix.
Defaults to subst,install.
--without=command[,command ...]
Inversely to the option above, this lists all the sub-commands which should not be used.
The list must not include the dh-exec- prefix.
--with-scripts=script[,script ...]
Replace the list of scripts to run the input through with a custom list (where entries are separated by whitespace or commas). This
option will always replace the existing list with whatever is specified.
This can be used to explicitly specify which scripts to use, limiting even beyond what the --with option is capable of.
The list must not include the dh-exec- prefix.
By default it is empty, meaning there is no filtering done, and whatever scripts the sub-commands find, will be run.
--no-act
Do not really do anything, but print the pipeline that would have been run instead.
--list
List the available sub-commands and scripts, grouped by sub-command.
--help, --version
Display a short help or the package version, respectively.
SUB-COMMANDS
dh-exec-subst
Substitutes various variables (either from the environment, or from dpkg-architecture(1)).
dh-exec-install
An extension to dh_install(1), that supports renaming files during the copy process, using a special syntax.
ENVIRONMENT
DH_EXEC_LIBDIR
The directory in which the wrapped sub-commands reside. Defaults to /usr/lib/dh-exec/.
DH_EXEC_SCRIPTDIR
The directory in which the scripts that do the heavy work live. Defaults to /usr/share/dh-exec/.
FILES
$DH_EXEC_LIBDIR/dh-exec-*
The various sub-commands.
$DH_EXEC_SCRIPTDIR/dh-exec-*
The various scripts ran by the sub-commands.
SEE ALSO
debhelper(1), dh-exec-subst(1), dh-exec-install(1)
AUTHOR
dh-exec is copyright (C) 2011-2012 by Gergely Nagy <algernon@madhouse-project.org>.
2012-05-03 DH-EXEC(1)