08-02-2001
Inter Process Communication
unix IPC
i would like to know the method of usage of semaphores on shared memory segments the topic seems very difficult to understand mainly when difrent proceses communicate instantly and how do i avaoid deadlock situation
10 More Discussions You Might Find Interesting
1. Programming
signal in process communication:
I 'm a example in sun_unix that signal in process communication
It's here down but I only have freebsd in my machine.
how can i do the same in freebsd
eg:
#include <stdio.h>
#include <signal.h>
#include <unistd.h>
int
main( void ){
void... (2 Replies)
Discussion started by: a9711
2 Replies
2. HP-UX
Hi All,
i am running a oracle procedure which writes a file . The same file is picked up by another script which runs in a cron after every 5 minutes.
Now the problem is that sometimes my script picks up a file while the procedure is still writing data in the file.
is there is any way i... (4 Replies)
Discussion started by: saurabhjain
4 Replies
3. Programming
Hello,
I would like to ask you for a little help with program I'm working on. I have problems with signals and synchronizing processes (I'm quite new to this part of programming).
Process "parent" creates new child process "child1" and this process creates new child process "child2". The... (2 Replies)
Discussion started by: Nightwright
2 Replies
4. UNIX for Advanced & Expert Users
Hi,
I am thinking about writing a log daemon for a multi-processed ksh application (yes - I know that high-level language would be a better option).
My question is as follows:
If many processes (many scripts) will try writing to a single log file:
print "message" > common.log
Will it work or... (2 Replies)
Discussion started by: adderek
2 Replies
5. Programming
i want to write a C chat program that communicates over IPC(inter process communication), that could be run using 2 seperate terminal windows within the same computer. so that wat u type in one terminal window , should appear on the other and vice versa...
could some one please help me with the... (2 Replies)
Discussion started by: localp
2 Replies
6. Programming
I need help!Many Thanks!
Now,I try to manage the shared memory inter-process .
Inevitably,I have to deal with the synchronous.
I know the pthread_rwlock in posix,and I compile ,then run successfully in Red Hat Enterprise 4.
I have a doubt about whether the Posix supports the system such as... (1 Reply)
Discussion started by: weizh
1 Replies
7. OS X (Apple)
If I open two bash shells and telnet from Shell 2 to a remote server (on the Net), is there a way to direct input from Shell 1 to the telnet shell?
The telnet shell is a limited environment with a specific command set.
I want to direct commands from Shell 1 and, if possible, put 1-second... (2 Replies)
Discussion started by: xinUoG
2 Replies
8. Programming
hello everyone,
i am making chat server in linux using c. i have made programs in which group chat can take place between multiple clients but i am not able to understand how to make 2 particular clients chat with each other. please help!!! (1 Reply)
Discussion started by: sweetbella
1 Replies
9. Programming
Hello
I would like to create an application with communication between processes,
application tightly coupled, have you please an idea about an API or
a tool that allows me to generate such application?
Thank you so much (11 Replies)
Discussion started by: chercheur857
11 Replies
10. IP Networking
Hello. I want to Communicate 2 VLAN with router like this solution:
http://8pic.ir/images/83m0ouih8mmm9s1sfl56.jpg
For this purpose I'm configuring 2 Linux system as a switch and connect 4 host to them. Then a router is added to scenario.
The configuration of the switches is:
On DUT1(Linux):... (1 Reply)
Discussion started by: zsn
1 Replies
IPCS(1) BSD General Commands Manual IPCS(1)
NAME
ipcs -- report System V interprocess communication facilities status
SYNOPSIS
ipcs [-abcmopqstMQST] [-C system] [-N core]
DESCRIPTION
The ipcs program provides information on System V interprocess communication (IPC) facilities on the system.
The options are as follows:
-a Show the maximum amount of information possible when displaying active semaphores, message queues, and shared memory segments. (This
is shorthand for specifying the -b, -c, -o, -p, and -t options.)
-b Show the maximum allowed sizes for active semaphores, message queues, and shared memory segments. The ``maximum allowed size'' is
the maximum number of bytes in a message on a message queue, the size of a shared memory segment, or the number of semaphores in a
set of semaphores.
-c Show the creator's name and group for active semaphores, message queues, and shared memory segments.
-m Display information about active shared memory segments.
-o Show outstanding usage for active message queues, and shared memory segments. The ``outstanding usage'' is the number of messages in
a message queue, or the number of processes attached to a shared memory segment.
-p Show the process ID information for active semaphores, message queues, and shared memory segments. The ``process ID information'' is
the last process to send a message to or receive a message from a message queue, the process that created a semaphore, or the last
process to attach or detach a shared memory segment.
-q Display information about active message queues.
-s Display information about active semaphores.
-t Show access times for active semaphores, message queues, and shared memory segments. The access times is the time of the last con-
trol operation on an IPC object, the last send or receive of a message, the last attach or detach of a shared memory segment, or the
last operation on a semaphore.
-C system
Extract the name list from the specified system instead of the default ``/netbsd''.
-M Display system information about shared memory.
-N core
Extract values associated with the name list from the specified core instead of the default ``/dev/kmem''. and semaphores.
-Q Display system information about messages queues.
-S Display system information about semaphores.
-T Display system information about shared memory, message queues and semaphores. (This is shorthand for specifying the -M, -Q, and -S
options.)
If none of the -M, -m, -Q, -q, -S, -s, or -T options are specified, information about all active IPC facilities is listed.
RESTRICTIONS
System data structures may change while ipcs is running; the output of ipcs is not guaranteed to be consistent.
FILES
/dev/kmem default kernel memory
/netbsd default system name list
SEE ALSO
ipcrm(1), shmat(2), shmctl(2), shmdt(2), shmget(2)
AUTHORS
Thorsten Lockert <tholo@sigmasoft.com>
BUGS
This manual page is woefully incomplete, because it does not at all attempt to explain the information printed by ipcs.
BSD
March 21, 2004 BSD