The idea here is to use predefined exit values for various error conditions.
When you see a unix command return an error code like 64, chances are the exit codes conform to the sysexits model. sysexits is a model, or a suggestion. But it does allow the program to convey intelligence when an error occurs.
For example the diff command (by POSIX standards) has it's own little protocol. It does not use sysexits because in part the information ( or meaning ) associated with two return codes of the three are not errors.
Code:
return value meaning
0 differences found
1 no differences found
2 some other error occurred
This parallels in part alister's comment about the "range" of return values.
Last edited by jim mcnamara; 11-06-2012 at 09:10 PM..
i just finished a project for a c++ class that i wrote at home on my computer, compiled with gcc. when i brought the code into school it would not compile, it would complain that cannot call main() function. at school we use ancient borland c++ from 1995. anyway my program has 20 different... (3 Replies)
What is the sytax to return an int from C program main back to calling shell?
#!/usr/bin/ksh
typeset -i NO_RECS
$NO_RECS=process_file
# Process file is a C program that is set up to return an int from main. The
#program complies with no issues, but an error is generated when the... (3 Replies)
Hi,
I have a main loop which calls a sub loop, which finally returns to the main loop itself. The main loop runs when a flag is set. Now, I have a signal handler for SIGINT, which resets the flag and thus stops the main loop. Suppose I send SIGINT while the program is in subloop, I get an error... (1 Reply)
Hi,
I am having issue with awk command . This command is running in the command prompt but inside a shell script.
awk -F'| ' 'int($1)==$1 && int($3) ==$3' int_check.txt
$cat int_check.txt
123|abc|123x
234|def|345
When i run it inside a shell script i am getting the error
"bailing... (5 Replies)
Hello, I have the below perl function int to return the integer value from the expression but it is not. I am not sure if something misses out here. Any help on this? Thanks in advance.
# Code sample Start
my $size = int (`1134 sample_text_here`);
print "$size \n";
# Code end
----------... (0 Replies)
Hi,
from the manual
listen(2): listen for connections on socket - Linux man page
It has a parameter called backlog and it limits the maximum length of queue of pending list.
If I set backlog to 128, is it means no more than 128 packets can be handled by server?
If I have three... (3 Replies)
Hi friends,
when I am passing arguments to main, I want another function to be able to have access to that function, the problem is that I am creating athread, which has a function like void *xyz(void *), how can pass the refernce of argv to this function, if you see my program, you will better... (2 Replies)
Hi. I have some code, that for some reason, I could not post it here in this post. Here's the address for it:
#if 0 shc Version 4.0.1, Generic Shell Script Compiler GNU GPL Version 3 Md - Pastebin.com
First off, I used "shc" to convert the code from shell script to C.
And The... (6 Replies)
Discussion started by: ignatius
6 Replies
LEARN ABOUT FREEBSD
introduction
INTRO(1) BSD General Commands Manual INTRO(1)NAME
intro -- introduction to general commands (tools and utilities)
DESCRIPTION
Section one of the manual contains most of the commands which comprise the BSD user environment. Some of the commands included in section
one are text editors, command shell interpreters, searching and sorting tools, file manipulation commands, system status commands, remote
file copy commands, mail commands, compilers and compiler tools, formatted output tools, and line printer commands.
All commands set a status value upon exit which may be tested to see if the command completed normally. Traditionally, the value 0 signifies
successful completion of the command, while a value >0 indicates an error. Some commands attempt to describe the nature of the failure by
using exit codes as defined in sysexits(3), while others simply set the status to an arbitrary value >0 (typically 1).
SEE ALSO apropos(1), man(1), intro(2), intro(3), sysexits(3), intro(4), intro(5), intro(6), intro(7), security(7), intro(8), intro(9)
Tutorials in the UNIX User's Manual Supplementary Documents.
HISTORY
The intro manual page appeared in Version 6 AT&T UNIX.
BSD October 21, 2001 BSD