I have written the below script but its not working as per expectation.
My requirement is if this condition [[ $missing_count -gt 0 ]] is satisfied
then only check for this condition [[ $parm==5 ]] if this also satisfied check for the condition [[ $val -eq $cnt ]].
Why if [[ $parm==5 ]]; then this condition is still satisfying even I passed 4 parameters .
Could you pleas help me.
Hi frnds...
I m facing very irritating problem already waisted my 2 days..
I have a following script..( i am pasting only the main code)
ftp -ivn 213.194.40.77 <<FTP
user $user $password
binary
cd $FileDir/out
lcd $localpath
get $file
rename $FileDir/out/$file $FileDir/tmp/$file... (1 Reply)
Well I have a 3000 lines result log file that contains all the machine data when it does the testing... It has 3 different section that i am intrsted in
1) starting with "20071126 11:11:11 Machine Header 1"
1000 lines...
"End machine header 1"
2) starting with "20071126 12:12:12 Machine... (5 Replies)
I have five classes. 2 composition classes,1 aggregation class and 1 dependency class.I have coded all the classes but one of my test program is not giving me the expected result.I have the following classes:
TimeStamp
Interval (composition of 2 TimeStamps)
TimeSheet ( aggregation of many... (3 Replies)
Hi All,
I write an script will have some functions... I am getting elif not expected error..
Even tried by using set -x for debug but no use..
Could you please help me out in this
Variables
....
....
....
TEST_SRC()
{
cat ${filesrc} >> ${filetgt}
if ]; then
echo... (12 Replies)
Hi Gurus,
I have requirement to compare current result with previous reuslt.
The sample case is below.
1 job1 1
1 job2 2
1 job3 3
2 job_a1 1
2 job_a2 2
2 job_a3 3
3 job_b1 1
3 job_b2 2
for above sample file, GID is group ID, for input line, the job run... (1 Reply)
Hello,
I am trying to print out the first string matching query with grep and I need your help.
My scenario:
Database
John F
4433 Street No 88 CA
Elisabeth Taylor
7733 Street No 26 ON
Jack Nicholson
0133 Green Park No 34 AR
John F 2
9399 Southpark No 02D UT
test.sh... (6 Replies)
Hi Gurus,
I run command grep ABC file1 > file2 against below file. I got all ABC_xxx in one line in file2. I expect to get multiple lines in file2. If I print result in screen, the result is expected.
thanks in advance
My os is SunOS 5.10 Generic_150400-64 sun4v sparc sun4v
ABC_123
XXXXX... (2 Replies)
Discussion started by: green_k
2 Replies
LEARN ABOUT V7
condition
condition(5) Standards, Environments, and Macros condition(5)NAME
condition - concepts related to condition variables
DESCRIPTION
Occasionally, a thread running within a mutex needs to wait for an event, in which case it blocks or sleeps. When a thread is waiting for
another thread to communicate its disposition, it uses a condition variable in conjunction with a mutex. Although a mutex is exclusive and
the code it protects is sharable (at certain moments), condition variables enable the synchronization of differing events that share a
mutex, but not necessarily data. Several condition variables may be used by threads to signal each other when a task is complete, which
then allows the next waiting thread to take ownership of the mutex.
A condition variable enables threads to atomically block and test the condition under the protection of a mutual exclusion lock (mutex)
until the condition is satisfied. If the condition is false, a thread blocks on a condition variable and atomically releases the mutex that
is waiting for the condition to change. If another thread changes the condition, it may wake up waiting threads by signaling the associated
condition variable. The waiting threads, upon awakening, reacquire the mutex and re-evaluate the condition.
Initialize
Condition variables and mutexes should be global. Condition variables that are allocated in writable memory can synchronize threads among
processes if they are shared by the cooperating processes (see mmap(2)) and are initialized for this purpose.
The scope of a condition variable is either intra-process or inter-process. This is dependent upon whether the argument is passed implic-
itly or explicitly to the initialization of that condition variable. A condition variable does not need to be explicitly initialized. A
condition variable is initialized with all zeros, by default, and its scope is set to within the calling process. For inter-process syn-
chronization, a condition variable must be initialized once, and only once, before use.
A condition variable must not be simultaneously initialized by multiple threads or re-initialized while in use by other threads.
Condition variables attributes may be set to the default or customized at initialization. POSIX threads even allow the default values to
be customized. Establishing these attributes varies depending upon whether POSIX or Solaris threads are used. Similar to the distinctions
between POSIX and Solaris thread creation, POSIX condition variables implement the default, intra-process, unless an attribute object is
modified for inter-process prior to the initialization of the condition variable. Solaris condition variables also implement as the
default, intra-process; however, they set this attribute according to the argument, type, passed to their initialization function.
Condition Wait
The condition wait interface allows a thread to wait for a condition and atomically release the associated mutex that it needs to hold to
check the condition. The thread waits for another thread to make the condition true and that thread's resulting call to signal and wakeup
the waiting thread.
Condition Signaling
A condition signal allows a thread to unblock the next thread waiting on the condition variable, whereas, a condition broadcast allows a
thread to unblock all threads waiting on the condition variable.
Destroy
The condition destroy functions destroy any state, but not the space, associated with the condition variable.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
SEE ALSO fork(2), mmap(2), setitimer(2), shmop(2), cond_broadcast(3C), cond_destroy(3C), cond_init(3C), cond_signal(3C), cond_timedwait(3C),
cond_wait(3C), pthread_cond_broadcast(3C), pthread_cond_destroy(3C), pthread_cond_init(3C), pthread_cond_signal(3C), pthread_cond_timed-
wait(3C), pthread_cond_wait(3C), pthread_condattr_init(3C), signal(3C), attributes(5), mutex(5), standards(5)NOTES
If more than one thread is blocked on a condition variable, the order in which threads are unblocked is determined by the scheduling pol-
icy.
USYNC_THREAD does not support multiple mapplings to the same logical synch object. If you need to mmap() a synch object to different loca-
tions within the same address space, then the synch object should be initialized as a shared object USYNC_PROCESS for Solaris, and
PTHREAD_PROCESS_PRIVATE for POSIX.
SunOS 5.10 20 Jul 1998 condition(5)