03-02-2005
How does one normally look into the web?
3 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I don't understand this, can anyone explain the evaluation logic used here, and I would really appreciate a general explanation for it.
----------------------
Here's the korn script:
--------------------
#! /usr/bin/ksh
if ]
then
echo true
else
echo false
fi
if (( 2 > 10 ))
then... (1 Reply)
Discussion started by: numstr
1 Replies
2. Shell Programming and Scripting
exam is a ksh script. In command line I enter: exam 3 param_2 param_3 param_4.
In exam how can I get the value of the parameter which position is specified by the first argument.
Simply doing this DOES NOT work:
offset=$1
value=$$offset
can you figure out any possible way to interpret a... (5 Replies)
Discussion started by: i27oak
5 Replies
3. UNIX for Dummies Questions & Answers
Hi all.
So I have a problem. I have been doing real good figuring this stuff out on my own but Im a newbie and stuck on something that is probably real basic.
I want to get the following output from the who command:
User TTY Date Time
gd22a12 pts/1 Feb 1 11:34
gd22a13 pts/3 Feb 1... (13 Replies)
Discussion started by: losingit
13 Replies
LEARN ABOUT REDHAT
assert_perror
ASSERT_PERROR(3) Linux Programmer's Manual ASSERT_PERROR(3)
NAME
assert_perror - test errnum and abort
SYNOPSIS
#include <assert.h>
void assert_perror(int errnum);
DESCRIPTION
If the macro NDEBUG was defined at the moment <assert.h> was last included, the macro assert_perror() generates no code, and hence does
nothing at all. Otherwise, the macro assert_perror() prints an error message to standard output and terminates the program by calling
abort() if errnum is nonzero. The message contains the filename, function name and line number of the macro call, and the output of str-
error(errnum).
RETURN VALUE
No value is returned.
CONFORMING TO
This is a GNU extension.
BUGS
The purpose of the assert macros is to help the programmer find bugs in his program, things that cannot happen unless there was a coding
mistake. However, with system or library calls the situation is rather different, and error returns can happen, and will happen, and
should be tested for. Not by an assert, where the test goes away when NDEBUG is defined, but by proper error handling code. Never use this
macro.
SEE ALSO
exit(3), abort(3), assert(3), strerror(3)
GNU
2002-08-25 ASSERT_PERROR(3)