Sponsored Content
Full Discussion: Inter Process Communication
Top Forums Programming Inter Process Communication Post 4883 by kamathanil on Thursday 2nd of August 2001 12:51:36 PM
Old 08-02-2001
Data 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

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 interprocess communication facilities status

Syntax
       ipcs [options]

Description
       The  command  provides  information about active, interprocess communication facilities, message queues, shared memory, and semaphores that
       are currently active in the system.

Options
       The information is displayed in columns and is controlled by the following options:

       -m     Displays information about active shared memory segments

       -q     Displays information about active message queues

       -s     Displays information about active semaphores

       If any of the options -q, -m, or -s are specified, information about only those indicated are printed.  If none of these  three	is  speci-
       fied, information about all three are printed.

       -a     Uses all print options (shorthand notation for -b, -c, -o, -p and -t)

       -b     Displays	the  biggest allowable size information (maximum number of bytes in messages on queue for message queues, size of segments
	      for shared memory, and number of semaphores in each set for semaphores)

       -C     Uses the specified core file (next argument) in place of

       -c     Displays creator's login name and group name

       -N     Uses the specified namelist (next argument) in place of

       -o     Displays the outstanding usage information  (number of messages in queue, size of each and number of processes  attached	to  shared
	      memory segments)

       -p     Displays	the  process ID information (process ID of last process to send a message and process ID of last process to receive a mes-
	      sage on message queues and process ID of creating process and process ID of last process to attach or detach on shared  memory  seg-
	      ments)

       -t     Displays	all  time  statistics  (time of the last control operation that changed the access permissions for all facilities, time of
	      last and last on message queues, last and last on shared memory, last on semaphores)

       The column headings and the meaning of the columns in an listing are given below.  The letters in parentheses  indicate	the  options  that
       cause the corresponding heading to appear; all means that the heading always appears.  Note that these options only determine what informa-
       tion is provided for each facility; they do not determine which facilities are listed.

       T (all)		   Type of facility:

			   q	  Message queue

			   m	  Shared memory segment

			   s	  Semaphore

       ID (all) 	   The identifier for the facility entry.

       KEY (all)	   The key used as an argument to or to create the facility entry.  Note:  The key of a shared memory segment  is  changed
			   to IPC_PRIVATE when the segment has been removed until all processes attached to the segment detach it.

       MODE (all)	   The facility access modes and flags.
			   The mode consists of 11 characters.	The first two characters are interpreted as follows:

			   R	  If the process is waiting on a

			   S	  If a process is waiting on a

			   D	  If  the  associated shared memory segment has been removed.  It disappears when the last process attached to the
				  segment detaches it.

			   C	  If the associated shared memory segment is to be clear when the first attach is executed.

			   -	  If the corresponding special flag is not set.

			   The next 9 characters are interpreted as three sets of three bits each.  The first set refers to  the  owner's  permis-
			   sions;  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 character indicates permission to write or alter the facility entry, and the last character is cur-
			   rently unused.
			   The permissions are indicated as follows:

			   r	  If read permission is granted

			   w	  If write permission is granted

			   a	  If alter permission is granted

			   -	  If the indicated permission is not granted

       OWNER (all)	   The login name of the owner of the facility entry.

       GROUP (all)	   The group name of the group of the owner of the facility entry.

       CREATOR (a,c)	   The login name of the creator of the facility entry.

       CGROUP (a,c)	   The group name of the group of the creator of the facility entry.

       CBYTES (a,o)	   The number of bytes in messages currently outstanding on the associated message queue.

       QNUM (a,o)	   The number of messages currently outstanding on the associated message queue.

       QBYTES (a,b)	   The maximum number of bytes allowed in messages outstanding on the associated message queue.

       LSPID (a,p)	   The process ID of the last process to send a message to the associated queue.

       LRPID (a,p)	   The process ID of the last process to receive a message from the associated queue.

       STIME (a,t)	   The time the last message was sent to the associated queue.

       RTIME (a,t)	   The time the last message was received from the associated queue.

       CTIME (a,t)	   The time the associated entry was created or changed.

       NATTCH (a,o)	   The number of processes attached to the associated shared memory segment.

       SEGSZ (a,b)	   The size of the associated shared memory segment.

       CPID (a,p)	   The process ID of the creator of the shared memory entry.

       LPID (a,p)	   The process ID of the last process to attach or detach the shared memory segment.

       ATIME (a,t)	   The time the last attach was completed to the associated shared memory segment.

       DTIME (a,t)	   The time the last detach was completed on the associated shared memory segment.

       NSEMS (a,b)	   The number of semaphores in the set associated with the semaphore entry.

       OTIME (a,t)	   The time the last semaphore operation was completed on the set associated with the semaphore entry.

Restrictions
       Things can change while is running.  The picture it gives is only a close approximation to reality.

Files
       /vmunix	 system namelist
       /dev/kmem memory
       /etc/passwd    user names
       /etc/group     group names

See Also
       ipcrm(2), msgop(2), semop(2), shmop(2)

																	   ipcs(1)
All times are GMT -4. The time now is 04:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy