05-19-2012
ZeroMQ, as suggested by agama, is surely a good tool, but I'd like to ask a question first: what exactly do you want to do and in which environment should it take place?
Inter-process communication (IPC) is a wide field and for some purposes a simple semaphor is enough while for others one needs shared memory, sockets and whatnot.
Without understanding what exactly you are trying to achieve it is hard to suggest anything.
I hope this helps.
bakunin
This User Gave Thanks to bakunin For This Post:
9 More Discussions You Might Find Interesting
1. Programming
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 (2 Replies)
Discussion started by: kamathanil
2 Replies
2. 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
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. UNIX for Dummies Questions & Answers
i need to develop application which continuously wait for a request from multiple host and on receiving a request on that need to create a log file and after 30 mins delete that file
I am new to socket programming so could anyone help me on this.
How to continuously listen for a request
How... (0 Replies)
Discussion started by: tryit
0 Replies
6. Linux
tcp communication application
i have an application which run in
1)
while()
{in
}
and listens for some request
When a request comes to create a file(containing some data fetch from somewhere)
but i also want to start some timer that after 10/20 min delete that file
But i don't know how... (0 Replies)
Discussion started by: tryit
0 Replies
7. 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
8. Shell Programming and Scripting
Dear All,
I need a help.
i have an mapped drive application. I want to start this application using cron. I have downloaded cron setup from the below link:
www.kalab.com/freeware/cron/cron.htm
And it crontab file works fine.
But if i want to start an application. Then process... (2 Replies)
Discussion started by: vasanth.vadalur
2 Replies
9. UNIX for Advanced & Expert Users
Hi All,
I am facing problem in launching a application with the help of a daemon process. Actually the application is based on command line that reads various commands for controlling the application from the console and accordingly executes those commands. The application always interact with... (3 Replies)
Discussion started by: gopallinux
3 Replies
IPCS(1) BSD General Commands Manual IPCS(1)
NAME
ipcs -- report System V interprocess communication facilities status
SYNOPSIS
ipcs [-abcMmopQqSsTt]
DESCRIPTION
The ipcs utility 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 system information about shared memory.
-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 system information about messages queues.
-q Display information about active message queues.
-S Display system information about semaphores.
-s Display information about active semaphores.
-T Display system information about shared memory, message queues and 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.
If none of the -M, -m, -Q, -q, -S, or -s 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.
BUGS
This manual page is woefully incomplete, because it does not at all attempt to explain the information printed by ipcs.
SEE ALSO
ipcrm(1)
AUTHORS
Thorsten Lockert <tholo@sigmasoft.com>
BSD
June 18, 1994 BSD