I cannot seem to pass the value of the variable assigned in the "else" statment below to an "if" statement outside of the loop. When I debug using "set -x", I find that the value of "$A" is empty. Is there something I'm missing here? Code is below:
do
if ] then
echo "Good Match"... (2 Replies)
Hi,
I have a strange problem and I'm sure its because I'm doing something stupid.
When I loop through all of the files in a directory they cannot be found.
Any help would be greatly appreciated.
Thanks,
-E
$ touch a.txt
$ touch b.txt
$ ls
a.txt b.txt
$ for f in `ls` ; do... (3 Replies)
can anyone please help me with this:
i have written a shell script and a stored procedure which has one OUT parameter. now i want to use that out parameter as an input to the unix script but i am getting an error as variable not found. below are the unix scripts and stored procedure...
... (4 Replies)
can any1 please tell me what is problem with following code:
i=1;
cat test| while read CMD;
do
Var$i=$CMD; or Var$i=$(echo $CMD) ;
let i++
doneI keep getting error :
line 4: Var1=sometext: command not found (2 Replies)
Hello All,
Maybe I'm Missing something here but I have NOOO idea what the heck is going on with this....?
I have a Variable that contains a PATTERN of what I'm considering "Illegal Characters". So what I'm doing is looping
through a string containing some of these "Illegal Characters". Now... (5 Replies)
Hi, I get a "FILEPATH: not found" error on the 3rd line and the line where it is within the case. Any idea as to why I'm getting this error time and time again?
Oh and FILEPATH will store the directory of the file.
I appreciate any help!
IAM=`basename $0`
RC=0
FILEPATH = ""... (1 Reply)
The code at the bottom is a simplified example of what we have.
If I use the following:
&& echo "echo failed"
$? returns 1
When I use
if ; then echo "echo failed" ; fi
$? returns 0
Does anyone know what's wrong with this?
Using AIX 6.1 and KSH
for NUM in 1 2 3
do
... (5 Replies)
I am unable to use the value of a variable.
while ]
do
LstFldDataPart =`head -n "$LstFldDataPartCntr" "${FeedFileDir}/${FeedFileBadRecs}" | tail -1 | tr -d '\n'`
echo $LstFldDataPart
JndLstFldDataPart="${JndLstFldDataPart}${LstFldDataPart}"
LstFldDataPartCntr=... (3 Replies)
Script name is test.ksh
I know that that the ssh command is working properly, this can be verified by the value returned in respond variable. It is unique to the remote server
_____________________________________________________
respond=$(ssh $remoteHost find... (3 Replies)
Discussion started by: Adagio
3 Replies
LEARN ABOUT HPUX
pthread_cond_broadcast
pthread_cond_signal(3T)pthread_cond_signal(3T)NAME
pthread_cond_signal(), pthread_cond_broadcast() - unblock one or all threads waiting on a condition variable
SYNOPSIS PARAMETERS
cond Pointer to the condition variable to be signaled or broadcast.
DESCRIPTION
The function is used to wake-up one of the threads that are waiting for the occurrence of a condition associated with condition variable
cond. If there are no threads blocked on cond, this function has no effect. If more than one thread is blocked on cond, the scheduling
policy determines which thread is unblocked. It is possible that more than one thread can be unblocked due to a spurious wakeup.
The function is used to wake-up all threads that are waiting for the occurrence of a condition associated with the condition variable cond.
If there are no threads blocked on cond, this function has no effect. If more than one thread is blocked on cond, the scheduling policy
determines the order in which threads are unblocked.
The condition variabled denoted by cond must have been dynamically initialized by a call to or statically initialized with the macro
An unblocked thread will reacquire the mutex it held when it started the condition wait before returning from or The threads that are
unblocked contend for the mutex according to their scheduling policy and priority.
The or functions can be called by a thread whether or not it currently owns the condition variable's associated mutex. For predictable
scheduling behavior and to prevent lost wake-ups, the mutex should be held when signaling a condition variable.
Usage
When using condition variables, there is a boolean predicate associated with each condition wait. If this predicate is false, the thread
should do a condition wait. Spurious wakeups may occur when waiting on a condition variable. Because the return values from and do not
imply anything about the value of this predicate, the predicate should always be re-evaluated.
Applications using condition variables typically acquire a mutex and enter a loop which checks the predicate. Depending on the value of
the predicate, the thread either breaks out of the loop or waits on the condition. On return from the condition wait, the predicate is re-
evaluated.
RETURN VALUE
Upon successful completion, and return zero. Otherwise, an error number is returned to indicate the error (the variable is not set).
ERRORS
For each of the following conditions, if the condition is detected, the and functions return the corresponding error number:
[EINVAL] cond is not a valid condition variable.
[EFAULT] cond parameter points to an illegal address.
AUTHOR
and were derived from the IEEE POSIX P1003.1c standard.
SEE ALSO pthread_cond_init(3T), pthread_cond_wait(3T).
STANDARDS CONFORMANCE
Pthread Library pthread_cond_signal(3T)