I have an if condition on executing it is giving syntax error as below:
--------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------
What may be the issue?
Line 61 code is as below:
--------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------
Please help.
Regards,
Ramki
Last edited by Scrutinizer; 08-06-2015 at 06:32 AM..
Reason: CODE tags
I do my backups using the following command
find / -print |cpio -ocv >/dve/rStp0
It has been working fine for ages and suddenly I am getting this error :-
Reached end of medium on output
If you want to go on type device/file name when ready
This happens after you press enter when... (1 Reply)
Hi All,
i have an small issue...
echo " "
eval x=$@
export x=`echo $x`
echo $x
ssh user@ipadrss; cd /mbbv/home/;
cd /mbbv/home/orange/orange/
echo pwd
bash samplescript.sh $x
above is my script which will triger from server A and will connect to server B for some... (2 Replies)
I have FreeBSD installed with Xarchiver and when extracting files through the file manager ("Extract here..." option) the following error pops up: tar: unrecognized option `--overwrite'
Perhaps this is a known error and is there a way to solve it? (10 Replies)
Hi,
I have installed Solaris 10 in my PC and now installing Oracle10, but while adding a user i am getting following error:
useradd -g oinstall -G dba -d /export/home/oracle oracle
UX: useradd: ERROR: Inconsistent password files. See pwconv(1M).
I have tried pwconv command,... (4 Replies)
Below part of script, is working fine sometimes and gives error sometime.
I am doing float operations, checking if x > y.
##########CODE##########
THRESHOLD="1.25"
ratio=$( echo "scale=2; ${prev}/${current}" | bc )
if ; then
split_date=`echo ${line} | cut -d, -f2`
fi ... (9 Replies)
Hi. I expect the following unix script command to return 8:
ls -ltr dropez* | grep -c dropez
I can't seem to find the correct syntax (borne shell), can anyone help be to write an IF condition something like this:
IF (ls -ltr dropez* | grep -c dropez) = 8 THEN
...do stuff
ELSE
...do... (4 Replies)
The syntax of 'if' conditionals in bash and ksh seems different. I am trying to check for a particular version using 'if' in ksh. This very simple syntax gives syntax error. I have tried many variants, but no go. Please correct the syntax. Later I will expand it to 'if' and 'else'.
#!/bin/ksh... (8 Replies)
Hi All,
We are getting a very unique error while running a shell script on HP-UX box.
Can somebody help in this regards?
The shell script is working fine on linux/solaris box.
Error:
++++++++++++++++++++++++
$/test.sh
./test.sh: 0^J30: Syntax error
$
++++++++++++++++++++++++
TIA.... (16 Replies)
Discussion started by: vai_sh
16 Replies
LEARN ABOUT HPUX
pthread_cond_destroy
pthread_cond_init(3T)pthread_cond_init(3T)NAME
pthread_cond_init(), pthread_cond_destroy() - initialize or destroy a condition variable
SYNOPSIS PARAMETERS
cond Pointer to the condition variable to be initialized or destroyed.
attr Pointer to the attributes object that defines the characteristics of the condition variable to be initialized. If the
pointer is NULL, default attributes are used.
DESCRIPTION
The function initializes the condition variable cond with the attributes attr. If attr is NULL, the default condition variable attributes
are used to initialize the attributes object. See pthread_condattr_init(3T) for a list of the default condition variable attributes.
After successful initialization, the condition variable may be used in condition variable operations. A condition variable should be ini-
tialized only once or the resulting behavior is undefined. The function provides a way to ensure that a condition variable is only ini-
tialized once.
The macro can be used to initialize condition variables that are statically allocated. These condition variables will be initialized with
default attributes. The function does not need to be called for statically initialized condition variables.
If the process-shared attribute in the condition variable attributes object referenced by attr is defined as the condition variable must be
allocated such that the processes sharing the condition variable have access to it. This may be done through the memory-mapping functions
(see mmap(2)) or the shared memory functions (see shmget(2)).
destroys the condition variable cond. This function may set cond to an invalid value. The destroyed condition variable can be reinitial-
ized using the function If the condition variable is used after destruction in any condition variable call, the resulting behavior is unde-
fined.
A condition variable should be destroyed only when there are no threads currently blocked on it. Destroying a condition variable that is
currently in use results in undefined behavior.
RETURN VALUE
Upon successful completion, and return zero. Otherwise, an error number is returned to indicate the error (the variable is not set).
ERRORS
If any of the following occur, the function returns the corresponding error number:
The system does not have the available resources (other than memory)
to initialize the condition variable.
The specified condition variable is an already initialized condition
variable. However, getting for reinitializing the condition variable cannot be expected all the time since the
behavior of reinitializing the condition variable is undefined.
The cond parameter points to an illegal address.
The value specified by
cond or attr is invalid.
There is insufficient memory available in which to initialize
the condition variable.
If any of the following occur, the function returns the corresponding error number:
An attempt to destroy
cond while it is in use by another thread.
cond is not a valid condition variable.
WARNINGS
The space for condition variable must be allocated before calling Undefined behavior will result if the process-shared attribute of attr is
and the space allocated for the condition variable is not accessible to cooperating threads.
AUTHOR
and were derived from the IEEE POSIX P1003.1c standard.
SEE ALSO pthread_cond_signal(3T), pthread_cond_wait(3T).
STANDARDS CONFORMANCE
Pthread Library pthread_cond_init(3T)