Sponsored Content
Full Discussion: Inter Process Communication
Top Forums Programming Inter Process Communication Post 5039 by mbb on Tuesday 7th of August 2001 06:32:58 AM
Old 08-07-2001
A very good book to read on the complete subject of IPC in Unix is
"Unix Network Programming"

by Prentice Hall

ISBN 0-13-949876-1

It just about covers the lot.

 

10 More Discussions You Might Find Interesting

1. Programming

signal in process communication

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

Inter Process File Handling Problem

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

Problem with signals - 3 process communication

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

Inter-process communication:pipes,doors,etc.

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

C program using IPC (inter process communication)

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

help with write-read locks inter-process

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)

Inter-shell communication

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

logic understanding for inter client chat server

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

Application with communication between process

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

Implement inter vlan routing with Linux

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) 						      General Commands Manual							   ipcs(1)

NAME
ipcs - report status of interprocess communication facilities SYNOPSIS
core] namelist] DESCRIPTION
displays certain information about active interprocess communication facilities. With no options, displays information in short format for the message queues, shared memory segments, and semaphores that are currently active in the system. Options The following options restrict the display to the corresponding facilities. (none) This is equivalent to Display information about active shared memory segments. Display information about active message queues. Display information about active semaphores. The following options add columns of data to the display. See "Column Description" below. (none) Display default columns: for all facilities: Display all columns, as appropriate. This is equivalent to Display largest-allowable-size information: for message queues: for shared memory segments: for semaphores: Display creator's login name and group name: for all facilities: Display information on outstanding usage: for message queues: for shared memory segments: Display process number information: for message queues: for shared memory segments: Display time information: for all facilities: for message queues: for shared memory segments: for semaphores: The following options redefine the sources of information. Use core in place of core can be a core file or a directory created by or Use file namelist or the namelist within core in place of It opens a crash dump for reading. Please refer to cr_open(3) for more details. Column Descriptions The column headings and the meaning of the columns in an listing are given below. The columns are printed from left to right in the order shown below. Facility type: Shared memory segment Message queue Semaphore The identifier for the facility entry. The key used as an argument to or to create the facility entry. (Note: The key of a shared memory segment is changed to when the segment has been removed until all processes attached to the segment detach it.) The facility access modes and flags: The mode consists of 11 characters that are interpreted as follows: The first two characters can be: A process is waiting on a A process is waiting on a The associated shared memory segment has been removed. It will disappear when the last process attached to the segment detaches it. The associated shared memory segment is to be cleared when the first attach is executed. The corresponding special flag is not set. The next 9 characters are interpreted as three sets of three characters each. The first set refers to the owner's permissions, the next to permissions of others in the group of the facility entry, and the last to all others. Within each set, the first character indicates permission to read, the second character indicates permission to write or alter the facility entry, and the last character is currently unused. Read permission is granted. Write permission is granted. Alter permission is granted. The indicated permission is not granted. The login name of the owner of the facility entry. The group name of the group of the owner of the facility entry. The login name of the creator of the facility entry. The group name of the group of the creator of the facility entry. The number of bytes in messages currently outstanding on the associated message queue. The number of messages currently outstanding on the associated message queue. The maximum number of bytes allowed in messages outstanding on the associated message queue. The process ID of the last process to send a message to the associated message queue. The process ID of the last process to receive a message from the associated message queue. The time the last message was sent to the associated message queue. The time the last message was received from the associated message queue. The time when the associated facility entry was created or changed. The number of processes attached to the associated shared memory segment. The size of the associated shared memory segment. The process ID of the creating process of the shared memory segment. The process ID of the last process to attach or detach the shared memory segment. The time the last attach was completed to the associated shared memory segment. The time the last detach was completed on the associated shared memory segment. The number of semaphores in the set associated with the semaphore entry. The time the last semaphore operation was completed on the set associated with the semaphore entry. WARNINGS
produces only an approximate indication of actual system status because system processes are continually changing while is acquiring the requested information. Do not rely on the exact field widths and spacing of the output, as these will vary depending on the system, the release of HP-UX, and the data to be displayed. FILES
Kernel virtual memory Group names User names System namelist SEE ALSO
msgop(2), semop(2), shmop(2). STANDARDS CONFORMANCE
ipcs(1)
All times are GMT -4. The time now is 05:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy