12-20-2008
what if i use semget semop and not use pthread_mutex_lock..
shall it work?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
I have an Producer/Consumer program in C(using shared memory and semaphores).It is working fine with sleep calls after every read/write operation.Each one is a independent program.Now if i remove the sleep calls in consumer,it goes on waiting in the loop till the producer puts some valid... (3 Replies)
Discussion started by: poorni_uma
3 Replies
2. UNIX for Dummies Questions & Answers
I would like to loop through a set of directories, performing operation(s) on each one. The basic script** is
dirs=`find . -name .svn -print`
for f in $dirs; do
echo "Processing $f directory .."
done
Fine and dandy, but here is the problem: the find expression must complete... (2 Replies)
Discussion started by: jakeo25
2 Replies
3. Programming
Control two exclusively shared resources. The two resources are two files. The producer will write even numbers to one file, and odd numbers to another one. The consumer respectively reads from each file until it gets 5 even numbers and 5 odd numbers.
Can any one help me with the code.
... (0 Replies)
Discussion started by: gokult
0 Replies
4. Shell Programming and Scripting
Control two exclusively shared resources. The two resources are two files. The producer will write even numbers to one file, and odd numbers to another one. The consumer respectively reads from each file until it gets 5 even numbers and 5 odd numbers.
Can any one help me with the code.
... (1 Reply)
Discussion started by: gokult
1 Replies
5. UNIX for Advanced & Expert Users
Control two exclusively shared resources(semaphore). The two resources are two files. The producer will write even numbers to one file, and odd numbers to another one. The consumer respectively reads from each file until it gets 5 even numbers and 5 odd numbers.
Can any one help me with the... (0 Replies)
Discussion started by: gokult
0 Replies
6. Programming
Control two exclusively shared resources(semaphore). The two resources are two files. The producer will write even numbers to one file, and odd numbers to another one. The consumer respectively reads from each file until it gets 5 even numbers and 5 odd numbers.
Can any one help me with the... (0 Replies)
Discussion started by: gokult
0 Replies
7. UNIX for Dummies Questions & Answers
Control two exclusively shared resources. The two resources are two files. The producer will write even numbers to one file, and odd numbers to another one. The consumer respectively reads from each file until it gets 5 even numbers and 5 odd numbers.
Can any one help me with the code.
... (3 Replies)
Discussion started by: gokult
3 Replies
8. Homework & Coursework Questions
Control two exclusively shared resources(semaphore). The two resources are two files. The producer will write even numbers to one file, and odd numbers to another one. The consumer respectively reads from each file until it gets 5 even numbers and 5 odd numbers.
Can any one help me with the... (1 Reply)
Discussion started by: gokult
1 Replies
9. UNIX for Dummies Questions & Answers
normally, i hate asking someone to do my homework for me but am getting desperate right now.
i have a project about consumer producer problem. the deadline is tonight at 23:55. but i havent gotten it working yet. i just COULDNT get it to work right yet.
the problem is as follows: the C - program... (0 Replies)
Discussion started by: alexantosh
0 Replies
10. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
normally, i hate asking someone to do my homework for me but am getting desperate right now.
i have a project... (1 Reply)
Discussion started by: alexantosh
1 Replies
LEARN ABOUT HPUX
core_addshmem_read
core_addshmem_read(5) File Formats Manual core_addshmem_read(5)
NAME
core_addshmem_read - determines the inclusion of readable shared memory in a process core dump
VALUES
Failsafe
Default
Allowed values
or
DESCRIPTION
The tunable was added in response to a problem where a customer was limited in debugging a user-level process crash because shared memory
segments were not written as part of the core file.
Upon core dump, the sections of user memory labeled as shared read-only are written (along with the normal data sections) if this tunable
is set to and left out if it is set to
Who is Expected to Change This Tunable?
Anyone.
Restrictions on Changing
Changes to this tunable take effect immediately.
When Should the Value of This Tunable Be Raised?
When you wish to include read-only shared memory segments in user core files due to debugging needs by developers or maintainers on the
system.
What Are the Side Effects of Raising the Value?
User process core files would increase in most cases (most applications use at least some shared memory). This could be a problem on sys-
tems where disk space is at a premium.
When Should the Value of This Tunable Be Lowered?
When there is no need for debugging core files where shared memory corruption or data values are in question.
What Are the Side Effects of Lowering the Value?
Core files will tend to be smaller.
What Other Tunable Values Should Be Changed at the Same Time?
Certainly think about which does the same thing for read/write shared memory segments.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
Tunable Kernel Parameters core_addshmem_read(5)