Sponsored Content
Full Discussion: fork() and IPC
Top Forums Programming fork() and IPC Post 2701 by Neo on Wednesday 30th of May 2001 03:57:45 PM
Old 05-30-2001
The primary way to share data between processes using UNIX IPCs are:

(1) Shared memory;

(2) Sockets:

There are other UNIX IPCs including

(3) Message Queues.

(4) Semaphores;

(5) Signals.

Your best best (for IPCs) is to use shared memory segments, based on your post. You might need to use semaphores to insure that the shared memory operations are atomic.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Ipc

I have a parent that is passing data to child A and then child A has to process it and pass to child B. I am able to pass the data to child A but am not able to pass it to child B. Child B seems to only be receiving the last data instead of the whole data. I saw one example in a book but it uses... (1 Reply)
Discussion started by: scmay
1 Replies

2. UNIX for Dummies Questions & Answers

Ipc Details

hai, i am doing my masters degree in computers.please any one tell me about fork(),semaphores,mutex,messaging queues,messaging using pipes ,and msgget(),msgrecv() funtions in ipc programming . i have exam on that i have a book but in that they not given clearly. hope u will ... (2 Replies)
Discussion started by: G.Vishnuvardhan
2 Replies

3. Programming

[C] Problem with IPC

Hi! I'm trying to write this program: in my intentions it should get a message and send it to a second process (pid_upost), then to a third process (pid1, pid2, pid3, depending on the choice made when a new message is inserted). This program should write the message in a file (message1, message2 or... (1 Reply)
Discussion started by: Kaminski
1 Replies

4. Programming

IPC with PIPE

Hi guys, I'm new to Linux and Unix I have just simple code . But I don't know why it doesn't work .. But, the outputfile is Blank.. I don't understand why.. Please help me.. Thank you very much P.S: sorry, I don't know how to edit this post clearly.. it's hard to read.. Please try.. (2 Replies)
Discussion started by: thanh_sam_khac
2 Replies

5. Solaris

errors on Netra-440: "IPC Warning: ipc: tcp_protocol: bad magic number"

I was asked to look into a problem with a Sun Netra 440 in another department. On the server in question, the relevant 'uname -a' information is, "SunOS host1 5.9 Generic_118558-16 sun4u sparc SUNW,Netra-440". That information aside, while the other admin is logged into the ALOM, these errors are... (0 Replies)
Discussion started by: Borealis
0 Replies

6. Programming

IPC Mechanisms

Hi! I wanted to know the advantages / disadvantages of different IPC mechanims such as sockets, pipes (unnamed) , shared memory & message queues. Pipes for example i hear are fast , but are difficult to debug as compared to sockets. Can you guys please name some situations where one is... (4 Replies)
Discussion started by: _korg
4 Replies

7. Programming

IPC-using fork() in a loop

I need to write a program which creates some n number of processes first and also creates a fifo for each of them, then it connects to the server and.. I tried creating these processes with fork() in a for loop but it doesn't print out what i write inside the child.. for(int count = 0; count... (7 Replies)
Discussion started by: saman_glorious
7 Replies

8. Programming

Best IPC mechanism to be used

Suppose I have 5 independent process divided in two imaginay sets: set1 set2 --------------------- p1 p3 | | p2 p4 | p5 The processes inside each set communicate mutually quite often. I mean p1 and p2 communicate mutually quite often Similarly p3, p4 and p5 communicate mutually... (2 Replies)
Discussion started by: rupeshkp728
2 Replies

9. HP-UX

IPC settings on HP-UX

Hi Experts, Need your help for checking te interprocess communications settings on HP-UX box. Using ipcs command I am able to view Message queue,semapohores etc, but from that output I m not able to understand how to determine if there is any issue with ipc settings and how to resolve that? (1 Reply)
Discussion started by: sai_2507
1 Replies

10. Shell Programming and Scripting

help with IPC + thread

Actually i am thinking of some usefull application that involves both IPC and pthreads.But i am not quite sure what type of application involves both these together :confused:. Anyways i am now working on creating a simple featured file manager that can do the following: Display file name and... (2 Replies)
Discussion started by: ronmaximus
2 Replies
ipcs(1) 						      General Commands Manual							   ipcs(1)

NAME
ipcs - Reports Interprocess Communication (IPC) facility status SYNOPSIS
ipcs [-a | -bcopt] [-mqs] [-C corefile] [-N namelist] The ipcs command writes to the standard output information about active Interprocess Communication (IPC) facilities. STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: ipcs: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
Same as specifying the -b, -c, -o, -p, and -t options. Writes the maximum number of bytes in message queues, the size of segments for shared memory, and the number of semaphores in each semaphore set. Writes the username and group name of the user that made the facility. Writes report based on contents of file corefile instead of /dev/kmem. Writes information about active shared memory segments. Writes report based on contents of file namelist instead of /vmunix. Writes the following usage information: Number of messages on queue Total number of bytes in message queues Number of processes attached to shared memory segments Writes the following: Process number of the last process to receive a message on message queues Process number of the creating process Process number of last process to attach or detach on shared memory segments Writes information about active message queues. Writes information about active semaphore set. Writes the follow- ing: Time of the last control operation that changed the access permissions for all facilities Time of the last msgsnd() and last msgrcv() on message queues Time of the last shmat() and last shmdt() on shared memory Time of the last semop() on semaphore sets DESCRIPTION
If you do not specify any options, ipcs writes information in a short form about currently active message queues, shared memory segments, semaphores, remote queues, and local queue headers. Column Headings The column headings and the meaning of the columns in an ipcs listing follow. The letters in parentheses indicate the flags that cause the corresponding heading to appear. The word all means that the heading always appears. The flags only determine what information is pro- vided for each facility; they do not determine which facilities are listed. Type of facility: Message queue Shared memory segment Sema- phore The identifier for the facility entry. The key used as a parameter to the msgget(), semget() or shemget() system calls to make the facility entry. Note that the key of a shared memory segment is changed to IPC_PRIVATE when the segment is removed. This change remains in effect 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: [Tru64 UNIX] If the associated shared memory segment was locked. If a process is waiting on a msgrcv() system call. If a process is waiting on a msgsnd() system call. If the associated shared memory segment was removed. It disappears when the last process attached to the segment detaches it. If the corresponding special flag is not set. The next nine characters are interpreted as three sets of three bits each. The first set refers to the owner's permissions, the next to permissions of others in the user group of the facility entry, and the last to all others. Within each set, the first char- acter indicates permission to read, the second character indicates permission to write or alter the facility entry, and the last character is currently unused. The permissions are indicated as follows: Read permission is granted. Write permission is granted. Alter permission is granted. The indicated permission is not granted. The username of the owner of the facility entry. The name of the group that owns the facility entry. The username of the creator of the facility entry. The group name of the group of the creator of the facility entry. Note that for the OWNER, GROUP, CREATOR, and CGROUP, the user and group IDs display instead of the usernames. 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 ID of the last process that sent a message to the associated queue. The ID of the last process that received a message from the associated queue. The time when the last message was sent to the associated queue. The time when the last message was received from the associated queue. The time when the associated 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 creator of the shared memory entry. The process ID of the last process to attach or detach the shared memory segment. The time when the last attach was completed to the associated shared memory segment. The time when the last detach was completed on the associated shared memory segment. The number of sema- phores in the set associated with the semaphore entry. The time when the last semaphore operation was completed on the set associ- ated with the semaphore entry. EXAMPLES
Sample output from entering ipcs without options follows. Message Queues: T ID KEY MODE OWNER GROUP q 4 0x41002ab4 --rw------- root system Shared Memory: T ID KEY MODE OWNER GROUP m 0 0x3253bc5c --rw-rw-rw- root system m 129 0 DLrw------- root daemon Semaphores: T ID KEY MODE OWNER GROUP s 0 0x41002ab4 --ra------- root system Output is formatted differently if the environment variable CMD_ENV is set to the string svr4. For example: IPC status from /dev/kmem as of Thu Mar 26 11:31:03 1998 T ID KEY MODE OWNER GROUP Message Queues: q 4 0x41002ab4 --rw------- root system Shared Memory: m 0 0x3253bc5c --rw-rw-rw- root system m 129 0 DLrw------- root daemon Semaphores: s 0 0x41002ab4 --ra------- root system FILES
Contains user information. Contains group information. SEE ALSO
Commands: ipcrm(1) Functions: msgrcv(2), msgsnd(2), semop(2), shmat(2), shmdt(2) ipcs(1)
All times are GMT -4. The time now is 01:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy