12-07-2004
try apropos exit code.... it will give a list of possible matches in the man pages.
moxxx68
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. 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. 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
5. 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
6. 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
7. 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
8. 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
9. 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
10. Shell Programming and Scripting
I have a script which connects to a remote server via FTP and gets some file from there.
#!/bin/bash
/usr/bin/ftp -n remote.hostname.com <<EOF
quote USER user123
quote PASS password123
lcd /dir1/dir2/dir3
cd /
mget file_pattern*
close
bye
EOF
rc=$?
if ]
... (7 Replies)
Discussion started by: dhruuv369
7 Replies
LEARN ABOUT MINIX
man.conf
MAN.CONF(5) File Formats Manual MAN.CONF(5)
NAME
man.conf - configuration file for man
DESCRIPTION
This is the configuration file for the man(1), apropos(1), and makewhatis(8) utilities. Its presence, and all directives, are optional.
This file is an ASCII text file. Leading whitespace on lines, lines starting with '#', and blank lines are ignored. Words are separated
by whitespace. The first word on each line is the name of a configuration directive.
The following directives are supported:
manpath path
Override the default search path for man(1), apropos(1), and makewhatis(8). It can be used multiple times to specify multiple
paths, with the order determining the manual page search order.
Each path is a tree containing subdirectories whose names consist of the strings 'man' and/or 'cat' followed by the names of
sections, usually single digits. The former are supposed to contain unformatted manual pages in mdoc(7) and/or man(7) format; file
names should end with the name of the section preceded by a dot. The latter should contain preformatted manual pages; file names
should end with '.0'.
Creating a mandoc.db(5) database with makewhatis(8) in each directory configured with manpath is recommended and necessary for
apropos(1) to work, but not strictly required for man(1).
output option [value]
Configure the default value of an output option. These directives are overridden by the -O command line options of the same names.
For details, see the mandoc(1) manual.
option value used by -T
fragment none html
includes string html
indent integer ascii, utf8
man string html
paper string ps, pdf
style string html
width integer ascii, utf8
_whatdb path/whatis.db
This directive provides the same functionality as manpath, but using a historic and misleading syntax. It is kept for backward
compatibility for now, but will eventually be removed.
FILES
/etc/man.conf
EXAMPLES
The following configuration file reproduces the defaults: installing it is equivalent to not having a man.conf file at all.
manpath /usr/share/man
manpath /usr/X11R6/man
manpath /usr/local/man
SEE ALSO
apropos(1), man(1), makewhatis(8)
HISTORY
A relatively complicated man.conf file format first appeared in 4.3BSD-Reno. For OpenBSD 5.8, it was redesigned from scratch, aiming for
simplicity.
AUTHORS
Ingo Schwarze <schwarze@openbsd.org>
Debian December 28, 2016 MAN.CONF(5)