05-05-2010
so there is no issue with if as you said.
and it check whether both invokes the same sqlplus ?
and are you running both from the same login ? and do that kind of debugging to find out.
10 More Discussions You Might Find Interesting
1. Programming
Where can a locate a list of Unix exit codes?
thank you,
Donna (3 Replies)
Discussion started by: donna carter
3 Replies
2. UNIX for Dummies Questions & Answers
I'm receiving an exit code 64 in our batch scheduler (BMC product control-m) executing a PERL script on UX-HP. Can you tell me where I can find a list of exit codes and their meaning. I'm assuming the exit code is from the Unix operating system not PERL. (3 Replies)
Discussion started by: jkuchar747
3 Replies
3. Shell Programming and Scripting
I have a Unix Script that has several exit in the middle. each returning seperate
exit codes.
I have to catch all the exit's and perform an operation say "Mail the status code" before the actual code completes.
How can i do this in KSH ? (3 Replies)
Discussion started by: Sivaswami J
3 Replies
4. UNIX for Advanced & Expert Users
Hi,
Can anyone give me the explanation for the exit codes 1 and 2 returned from Korn shell.
Thanks in advance. (1 Reply)
Discussion started by: sesedada
1 Replies
5. Tips and Tutorials
The most common Solaris exit codes you will see is 2 or 8, but have you ever had a different exit code and wondered what it means ?
Well you need not wonder no more...
Patch Exit Codes
----------------
0 No error
1 Usage error
2 Attempt to apply a patch that's already... (1 Reply)
Discussion started by: Tornado
1 Replies
6. Shell Programming and Scripting
HI All,
I have created a unix script which takes 2 parameters and using sftp tranfers files to remote location
following is the script
#!/bin/ksh
#
#
# Parameter 1 is the complete path of the destination server
# Parameter 2 is the complete path of the file which is to be FTP... (1 Reply)
Discussion started by: vikramsnest
1 Replies
7. Shell Programming and Scripting
I know that the exit codes in scripting "$*" will returns all the parameters/arguments passwd to the script.
But I also know that "$@" will also returns the same. What is the difference between those two ? (1 Reply)
Discussion started by: praveen_b744
1 Replies
8. Shell Programming and Scripting
Good Morning All..
I was wondering about getting exit codes of a command in a shell script. I'm trying to run uvscan (McAfee command line scanner) and I want to have the log file say why, if at all, the process failed/exited.
Something to the extent of
If ; then
echo "This is why it... (1 Reply)
Discussion started by: cmschube
1 Replies
9. Shell Programming and Scripting
Hello,
I need to ensure that SCP does not leave any partially transmitted files on the remote server due to transmission errors.
Can it be assumed that:
1) if SCP returns a success with Exit Code == 0, a complete local file has been copied in its entirety to the remote location?
2)... (1 Reply)
Discussion started by: rogersed
1 Replies
10. UNIX for Dummies Questions & Answers
how do i/is there a way to return the exit code from the remote host?
echo $? from the local host only gives 0, if the rexec command itself executes successfully. But what if in the case of the remote command failiing? echo $? on the localhost still gives 0, but I'm interested in the exit code... (4 Replies)
Discussion started by: diego_sapphire
4 Replies
WRITE(1) Linux Programmer's Manual WRITE(1)
NAME
write - send a message to another user
SYNOPSIS
write user [ttyname]
DESCRIPTION
Write allows you to communicate with other users, by copying lines from your terminal to theirs.
When you run the write command, the user you are writing to gets a message of the form:
Message from yourname@yourhost on yourtty at hh:mm ...
Any further lines you enter will be copied to the specified user's terminal. If the other user wants to reply, they must run write as
well.
When you are done, type an end-of-file or interrupt character. The other user will see the message EOF indicating that the conversation is
over.
You can prevent people (other than the super-user) from writing to you with the mesg(1) command. Some commands, for example nroff(1) and
pr(1), may disallow writing automatically, so that your output isn't overwritten.
If the user you want to write to is logged in on more than one terminal, you can specify which terminal to write to by specifying the ter-
minal name as the second operand to the write command. Alternatively, you can let write select one of the terminals - it will pick the one
with the shortest idle time. This is so that if the user is logged in at work and also dialed up from home, the message will go to the
right place.
The traditional protocol for writing to someone is that the string `-o', either at the end of a line or on a line by itself, means that
it's the other person's turn to talk. The string `oo' means that the person believes the conversation to be over.
SEE ALSO
mesg(1), talk(1), who(1)
HISTORY
A write command appeared in Version 6 AT&T UNIX.
AVAILABILITY
The write command is part of the util-linux-ng package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/.
12 March 1995 WRITE(1)