Hi all,
I've been trying for hours to figure out how to turn my 2-program (one to send and one to receive) "chat system" using message queues, into a single program where each concurrent component (entity) will both send and receive messages. PLEASE give me a hand with this, I'm starting to... (9 Replies)
let 3 processes a, b and c are sharing msgs using msg queues.process 'a' sending msg to 'c' and in turn 'c' send sthat msg to 'b'.if something happens to c how can 'a' and 'b' know that 'c' is not available?????? (2 Replies)
We have message queues created from our ERP system to our tax system via an application api written by the ERP software vendor.
Occasionally when a user does not gracefully exit the ERP application, the message queue hangs. After a few months, this becomes a problem as the queues are all used... (2 Replies)
Hi,
According to my understanding..
When message queues are used, when a process post a message in the queue and if another process reads it from the queue then the queue will be empty unlike shared memory where n number of processess can access the shared memory and still the contents remain... (2 Replies)
If I use sockets for IPC, and can easily distribute my applications.
UNIX Message Queues are local to the processor.
As I understand it, Message Queues still incur system call overhead, just like socket calls.
What advantage does a UNIX Message Queue provide versus a TCP or UDP Socket,... (2 Replies)
Hi,
Am supposed to use message queues to send and receive messages between the processes. when i was working on that i realised that the message qid and the message queue related data should be maintained in a shared memory so that it can be accessed by all the processes. Could anybody refer... (10 Replies)
#include <sys/ipc.h>
#include <sys/msg.h>
int main()
{
int qid;
int t;
struct msgbuf mesg;
qid=msgget(IPC_PRIVATE,IPC_CREAT);
mesg.mtype=1L;
mesg.mtext=1;
t=msgsnd(qid,&mesg,1,0);
printf("%d",t);
}
the program prints -1 as the result of msgsnd ,which means that msgsnd doesn't... (1 Reply)
i have an application installed on AIX 5.3 and i have made a script that shutdown a proccesses that exceeded 10000kb of memory usage but i have a problem with cleaning the message queues of these proccesses after shutting them down. Is there any way to clean the message queues for this particular... (8 Replies)
Discussion started by: Portabello
8 Replies
LEARN ABOUT FREEBSD
uname
UNAME(1) BSD General Commands Manual UNAME(1)NAME
uname -- display information about the system
SYNOPSIS
uname [-aiKmnoprsUv]
DESCRIPTION
The uname command writes the name of the operating system implementation to standard output. When options are specified, strings represent-
ing one or more system characteristics are written to standard output.
The options are as follows:
-a Behave as though the options -m, -n, -r, -s, and -v were specified.
-i Write the kernel ident to standard output.
-K Write the FreeBSD version of the kernel.
-m Write the type of the current hardware platform to standard output.
-n Write the name of the system to standard output.
-o This is a synonym for the -s option, for compatibility with other systems.
-p Write the type of the machine processor architecture to standard output.
-r Write the current release level of the operating system to standard output.
-s Write the name of the operating system implementation to standard output.
-U Write the FreeBSD version of the user environment.
-v Write the version level of this release of the operating system to standard output.
If the -a flag is specified, or multiple flags are specified, all output is written on a single line, separated by spaces.
The -K and -U flags are intended to be used for fine grain differentiation of incremental FreeBSD development and user visible changes.
ENVIRONMENT
An environment variable composed of the string UNAME_ followed by any flag to the uname utility (except for -a) will allow the corresponding
data to be set to the contents of the environment variable.
EXIT STATUS
The uname utility exits 0 on success, and >0 if an error occurs.
SEE ALSO feature_present(3), getosreldate(3), sysctl(3), uname(3), sysctl(8)STANDARDS
The uname command is expected to conform to the IEEE Std 1003.2 (``POSIX.2'') specification.
HISTORY
The uname command appeared in PWB UNIX.
The -K and -U extension flags appeared in FreeBSD 10.0.
BSD November 20, 2013 BSD