05-31-2001
Good reply and suggestion! I always read the source and forgot about the MAN pages!!
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. 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
5. 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
6. 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
7. 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
8. 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
9. 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
10. Linux
I am trying to run this SH on Linux and getting error at IF condition.
I want to read the EXIT code and send the failure or success message.
Please help me on this. This worked when i was running on Solaris.
#!/bin/bash
$ORACLE_HOME/bin/sqlplus abc/xyz@qwe @/home/test.sql
if ;... (4 Replies)
Discussion started by: rlmadhav
4 Replies
MAN(1) General Commands Manual MAN(1)
NAME
man - print sections of this manual
SYNOPSIS
man [ option ... ] [ chapter ] title ...
DESCRIPTION
Man locates and prints the section of this manual named title in the specified chapter. (In this context, the word `page' is often used as
a synonym for `section'.) The title is entered in lower case. The chapter number does not need a letter suffix. If no chapter is speci-
fied, the whole manual is searched for title and all occurrences of it are printed.
Options and their meanings are:
-t Phototypeset the section using troff(1).
-n Print the section on the standard output using nroff(1).
-k Display the output on a Tektronix 4014 terminal using troff(1) and tc(1).
-e Appended or prefixed to any of the above causes the manual section to be preprocessed by neqn or eqn(1); -e alone means -te.
-w Print the path names of the manual sections, but do not print the sections themselves.
(default)
Copy an already formatted manual section to the terminal, or, if none is available, act as -n. It may be necessary to use a filter
to adapt the output to the particular terminal's characteristics.
Further options, e.g. to specify the kind of terminal you have, are passed on to troff(1) or nroff. Options and chapter may be changed
before each title.
For example:
man man
would reproduce this section, as well as any other sections named man that may exist in other chapters of the manual, e.g. man(7).
FILES
/usr/man/man?/*
/usr/man/cat?/*
SEE ALSO
nroff(1), eqn(1), tc(1), man(7)
BUGS
The manual is supposed to be reproducible either on a phototypesetter or on a terminal. However, on a terminal some information is neces-
sarily lost.
MAN(1)