06-03-2010
passing database password to isql command in shell script
Hi,
I need to connect to DB through my shell script. but I dont want to hardcode my db password in the script. Is there a way to do it?
Thanks
---------- Post updated at 07:42 PM ---------- Previous update was at 04:54 PM ----------
Guys..please help me with this
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Anybody help to write a shell script as below requirement.
script stops some costomized application services.
1. first it will stop apache as root
2. then it will switch to my application user and stop app service.
Note: passing password is required to stop app service as app... (1 Reply)
Discussion started by: manojbarot1
1 Replies
2. Shell Programming and Scripting
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
3. Shell Programming and Scripting
Hi..
I am passing a variable in my shell function. I need to access it for an isql comand in the shell script.
However the isql o/p gives no results if i pass a variable in the command. The isql command works perfectly fine if i hardcore the table name.
My script is :
... (0 Replies)
Discussion started by: dikki
0 Replies
4. Shell Programming and Scripting
I have a requirement, I need to run a command at remote system using a ssh. Is there any way we can pass the username and password in shell script to the ssh command as we did it in one of the shell script for FTP.
ftp -n $i <<!EOF >>
user Username $PASSWD
cd /home/scripts
... (5 Replies)
Discussion started by: Muktesh
5 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I have a very small requirement where i need to pass command output as an argument while invoking the shell script..
I need to call like this
sh testscript.sh ' ls -t Appl*and*abc* | head -n 1'
This will list one file name as ana argument..
I will be using "$1" in the shell... (2 Replies)
Discussion started by: pssandeep
2 Replies
6. Shell Programming and Scripting
Hi all,
I have the expect binaries in our boxes..
I want to pass a passwd to a command automatically without manual intervention using "/<path_of_expect>/expect/<version>/bin/autopasswd"
The below command will ask passwd in my script
cleartool rmtag -all <vob_tag>
#Some... (4 Replies)
Discussion started by: raghu.iv85
4 Replies
7. Shell Programming and Scripting
I'm pretty new to bash scripting and I've found myself writing things like this (and the same with even more nesting):
if $CATEGORIES; then
if $LABEL_SLOTS; then
$pyth "$wd/texify_grammar.py" "$input" "$texfile" "--label-slots" "--categories" "$CATEGORY_LIST"
... (9 Replies)
Discussion started by: burbly
9 Replies
8. Shell Programming and Scripting
Hi Experts,
I have specific requirement where I want to pass the password with the ssh username@hostname command .
I dont want to use RSA public and private keys also. Because that will be on production server and no one wants to give access like that.
Second thing it is production... (14 Replies)
Discussion started by: sharsour
14 Replies
9. UNIX for Dummies Questions & Answers
I have a shell script (.sh) and I want to pass a parameter value to the awk command but I am getting exception, please assist.
diff=$1$2.diff
id=$2 new=new_$diff
echo "My id is $1"
echo "I want to sync for user account $id"
##awk command I am using is as below
cat $diff |... (1 Reply)
Discussion started by: Sarita Behera
1 Replies
10. Shell Programming and Scripting
Hi,
I have a shell script (script.sh) in which we are calling java code which asks for
Username:
Password:
for authentication purpose
currently we are passing the credential manually and run the script.
but I am trying
echo -e "user_id\npassword" | script.sh
but its not... (1 Reply)
Discussion started by: rakeshtomar82
1 Replies
exit(1) User Commands exit(1)
NAME
exit, return, goto - shell built-in functions to enable the execution of the shell to advance beyond its sequence of steps
SYNOPSIS
sh
exit [n]
return [n]
csh
exit [ ( expr )]
goto label
ksh
*exit [n]
*return [n]
DESCRIPTION
sh
exit will cause the calling shell or shell script to exit with the exit status specified by n. If n is omitted the exit status is that of
the last command executed (an EOF will also cause the shell to exit.)
return causes a function to exit with the return value specified by n. If n is omitted, the return status is that of the last command exe-
cuted.
csh
exit will cause the calling shell or shell script to exit, either with the value of the status variable or with the value specified by the
expression expr.
The goto built-in uses a specified label as a search string amongst commands. The shell rewinds its input as much as possible and searches
for a line of the form label: possibly preceded by space or tab characters. Execution continues after the indicated line. It is an error to
jump to a label that occurs between a while or for built-in command and its corresponding end.
ksh
exit will cause the calling shell or shell script to exit with the exit status specified by n. The value will be the least significant 8
bits of the specified status. If n is omitted then the exit status is that of the last command executed. When exit occurs when executing
a trap, the last command refers to the command that executed before the trap was invoked. An end-of-file will also cause the shell to exit
except for a shell which has the ignoreeof option (See set below) turned on.
return causes a shell function or '.' script to return to the invoking script with the return status specified by n. The value will be the
least significant 8 bits of the specified status. If n is omitted then the return status is that of the last command executed. If return
is invoked while not in a function or a '.' script, then it is the same as an exit.
On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari-
able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not
performed.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
break(1), csh(1), ksh(1), sh(1), attributes(5)
SunOS 5.10 15 Apr 1994 exit(1)