Condition:
At times a job might not have any condition in them , in that case the script should print as "No_Condition".
I am not able to figure out how to write the code that can check if condition string does not exist then print "No_Condition". Can someone please help me out.
Also i was thinking if we can consider from the line that begins with /* to the line before the next /* as one record and do some processing. But was not sure how to implement the same.
suppose if u have a file like that
Hen ABCCSGSGSGJJJJK 15
Cock ABCCSGGGSGIJJJL 15
* * * * * * : * * * . * * * :
Hen CFCDFCSDFCDERTF 30
Cock CHCDFCSDHCDEGFI 30
* . * * * * * * * : * * :* : : .
The output shud be
where there is : and .
It shud... (4 Replies)
Hello,
I'm new to shell scripting and did a search on the forum to what I want to do but couldn't find anything.
I have about 9 routers that outputs to 1 syslog file daily named cisco.year.mo.date.log ex: cisco.2009.05.11.log
My goal is to make a parsing script that cats today's syslog... (2 Replies)
hi guys,
i want to parse a file using public function, the file contain raw data in the below format i want to get the output like this to load it to Oracle DB
MARWA1,BSS:26,1,3,0,0,0,0,0.00,22,22,22.00
MARWA2,BSS:26,1,3,0,0,0,0,0.00,22,22,22.00
this the file raw format:
Number of... (6 Replies)
Hi all,
Is it possible to create an script that parse an snoop output similar to the example above ? Each line is ended by "$" (set list in vi). as a result, I would like to print the output in only one line.
can someone give me some tip ?
Thanks a lot .:)
l version="1.0" ... (5 Replies)
Hi I have the following as input
/* ----------------- backupJIL ----------------- */
insert_job: backupJIL job_type: c
command: autorep -J ALL -q > /home/autosys/...p/autosys_jil_bk
machine: machine
owner: autosys@machine
permission: gx,ge,wx,we
date_conditions: 1
days_of_week:... (7 Replies)
I'm trying to modify the script given in post 7 of the following thread: 146564-need-parse-jil-file-into-excel-file.html. (Sorry, can't post the URL as I don't have enough posts.)
The original script is as follows:
awk -F ' *_]*: *' 'BEGIN ... (9 Replies)
Output of the below code includes unmatched date.Please correct it
df -k|awk '$4>50 {print $1, "\t"$4,"\t" $7}'
It gives output less than 50% also. (5 Replies)
My source file looks like this:
Cust-Number = "101"
Cust-Name="Joe"
Cust-Town="London"
Cust-hobby="tennis"
Cust-purchase="200"
Cust-Number = "102"
Cust-Name="Mary"
Cust-Town="Newyork"
Cust-hobby="reading"
Cust-purchase="125"
Now I want to parse this file (leaving out hobby) and... (10 Replies)
Hello,
I am trying to write a script to parse the output of data and then alert based on certain conditions
This is the output of my script
(STRING) Name = Joe
(FLOAT64) BMI = 34
(FLOAT64) Weight = 156
(STRING) Name = Sam
(FLOAT64) BMI = 32
(FLOAT64) Weight = 180
and so on it repeats... (4 Replies)
Discussion started by: sidnow
4 Replies
LEARN ABOUT DEBIAN
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)