|
|
Sponsored Content
|
|
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
LEARN ABOUT MINIX
man
MAN(1) General Commands Manual MAN(1) NAME
man - display online manual pages SYNOPSIS
man [-antkf] [-M path] [-s section] title ... DESCRIPTION
Man displays the online manual pages for the specified titles in the specified sections. The sections are as follows: 1 User Commands Generic commands such as ls, cp, grep. 2 System Calls Low level routines that directly interface with the kernel. 3 Library Routines Higher level C language subroutines. 4 Device Files Describes devices in /dev. 5 File Formats Formats of files handled by various utilities and subroutines. 6 Games It's not UNIX without an adventure game. 7 Miscellaneous Macro packages, miscellaneous tidbits. 8 System Utilities Commands for the System Administrator. 9 Documents Larger manuals explaining some commands in more detail. (If you are new to Minix then try man hier, it will show you around the file system and give you many pointers to other manual pages.) By default, man will try the following files in a manual page directory for the command man -s 1 ls: cat1/ls.1 cat1/ls.1.Z man1/ls.1 man1/ls.1.Z Files in the man[1-8] directories are formatted with nroff -man. Those in man9 are formatted with nroff -mnx. Files in the cat? directo- ries are preformatted. Files with names ending in .Z are decompressed first with zcat (see compress(1)). The end result is presented to the user using a pager if displaying on the screen. For each manual page directory in its search path, man will first try all the subdirectories of the manual page directory for the files above, and then the directory itself. The directory /usr/man contains the standard manual pages, with manual pages for optional packages installed in a subdirectory of /usr/man, with the same structure as /usr/man. The directory /usr/local/man contains manual pages for locally added software. By default /usr/local/man is searched first, then /usr/man. A title is not simply used as a filename, because several titles may refer to the same manual page. Each manual page directory contains a database of titles in the whatis(5) file that is created by makewhatis(8) from the NAME sections of all the manual pages. A title is searched in this database and the first title on a whatis line is used as a filename. OPTIONS
The options may be interspersed with the titles to search, and take effect for the titles after them. -a Show all the manual pages or one line descriptions with the given title in all the specified sections in all the manual directories in the search path. Normally only the first page found is shown. -n Use nroff -man to format manual pages (default). -t Use troff -man to format manual pages. -f Use whatis(1) to show a one line description of the title from the whatis(5) file. -k Use apropos(1) to show all the one line descriptions of the title anywhere in the whatis(5) files (implies -a). -M path Use path as the search path for manual directories. -s section Section is the section number the page is to be found in, or a comma separated list of sections to use. Normally all sections are searched. The search is always in numerical order no matter what your section list looks like. A single digit is treated as a sec- tion number without the -s for compatibility with BSD-style man commands. ENVIRONMENT
MANPATH This is a colon separated list of directories to search for manual pages, by default /usr/local/man:/usr/man. PAGER The program to use to display the manual page or one line descriptions on the screen page by page. By default more. FILES
/usr/man/whatis One of the whatis(5) databases. SEE ALSO
nroff(1), troff(1), more(1), whatis(1), makewhatis(1), catman(1), whatis(5), man(7). AUTHOR
Kees J. Bot (kjb@cs.vu.nl) MAN(1)