"exit" will always exit, the number is the result code returned by the script from which you exited. An exit code of zero conventionally means "no error", any other number is treated as an error. This doesn't really matter if you are simply ignoring the exit code; but returning a meaningful exit code is useful so that you can use the script from another script.
Hi friends, :)
In a shell script i found the following if condition.
echo -n "Which version of $1 do you want to restore ('0' to quit)? : "
read desired
if ${desired:=1} -ge $index ] ; then
echo "$0: Restore canceled by user: index value too big." >&2
exit 1
fi
Can... (1 Reply)
i have a paramter data_date in which i am passing a string value.i want to find out another paramter file_date from this.the logic is given below
if day of data_date = sunday or monday
then
file_date=data_date-1
else
file_date=data_date-2
i am passing data_date as 20061027.
how can i... (3 Replies)
Hi,
I am trying to execute this command, but is it not working, says "`;' unexpected"
eval $lgrep $SAM_CMD ; if ; then ; echo "No Error" ; fi
What i want is, return the command output, if it is non zero, say "No Error".
Thanks, John. (21 Replies)
Executed the following if conditions .. and got different results .
only (( )) gave correct o/p with all scenarios .
Can anybody please let me know what is the difference between and ] and ((condition)) when used with if condition.
And why each condition gave different result.
1.... (2 Replies)
hi,
I have some problems in my simple script about the redirect echo stdout command inside a condition. Why is the echo command inside the elif still execute in the else command
Here are my simple script
After check on the two diff output the echo stdout redirect is present in two diff... (3 Replies)
HI
My doubt may be basic one but I need to get it clarified..
When i use "if" condition that checks for many AND, OR logical conditions
like
if ]; then
return 0
fi
Even the if condition fails it returns as zero.. Any clue..
But if i add else condition like
if ]; ... (2 Replies)
Hi all
Unix newbie - please be gentle
Am modifying an existing script to error trap a variable with a length of 0
#!/bin/bash
ipfile='/var/data/bin/ipaddress'
] && ipold="$(< "$ipfile" )"
ipnew="$( wget -q -O - checkip.dyndns.org | sed -e 's/.*Current IP Address: //;s/<.*$//' )"
#... (6 Replies)
o/p of my command is given below
My requirement is
if Pnumber is 0 then
stabilization.Build.2013
else
stabilization.PBuild.2013.3 (11 Replies)
Discussion started by: nikhil jain
11 Replies
LEARN ABOUT OSF1
pthread_cond_init
pthread_cond_init(3) Library Functions Manual pthread_cond_init(3)NAME
pthread_cond_init - Initializes a condition variable.
LIBRARY
DECthreads POSIX 1003.1c Library (libpthread.so)
SYNOPSIS
#include <pthread.h>
int pthread_cond_init(
pthread_cond_t *cond,
const pthread_condattr_t *attr);
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
IEEE Std 1003.1c-1995, POSIX System Application Program Interface
PARAMETERS
Condition variable to be initialized. Condition variable attributes object that defines the characteristics of the condition variable to
be initialized.
DESCRIPTION
This routine initializes the condition variable (cond) with attributes referenced by attr. If attr is NULL, the default condition variable
attributes are used.
A condition variable is a synchronization object used in conjunction with a mutex. A mutex controls access to data that is shared among
threads; a condition variable allows threads to wait for that data to enter a defined state.
Condition variables are not owned by a particular thread. Any associated storage is not automatically deallocated when the creating thread
terminates.
Use the DECthreads macro PTHREAD_COND_INITIALIZER to initialize statically allocated condition variables to the default condition variable
attributes. To call this macro, enter:
pthread_cond_t condition = PTHREAD_COND_INITIALIZER
When statically initialized, a condition variable should not also be using pthread_cond_init(3). Also, a statically initialized condition
variable need not be destroyed using pthread_cond_destroy(3).
Under certain circumstances, it might be impossible to wait upon a statically initialized condition variable when the process virtual
address space (or some other memory limit) is nearly exhausted. In such a case, pthread_cond_wait(3) or pthread_cond_timedwait(3) can
return [ENOMEM]. To avoid this possibility, initialize critical condition variables using pthread_cond_init(3).
RETURN VALUES
If an error condition occurs, this routine returns an integer value indicating the type of error, the condition variable is not initial-
ized, and the contents of cond are undefined. Possible return values are as follows: Successful completion. The system lacks the neces-
sary resources to initialize another condition variable, or The system-imposed limit on the total number of condition variables under exe-
cution by a single user is exceeded. The implementation has detected an attempt to reinitialize the object referenced by cond, a previ-
ously initialized, but not yet destroyed condition variable. The value specified by attr is invalid. Insufficient memory exists to ini-
tialize the condition variable.
ERRORS
None
RELATED INFORMATION
Functions: pthread_cond_broadcast(3), pthread_cond_destroy(3), pthread_cond_signal(3), pthread_cond_timedwait(3), pthread_cond_wait(3)
Manuals: Guide to DECthreads and Programmer's Guide
delim off
pthread_cond_init(3)