System V IPC problems Post: 302339584

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Prints Problems on Unix system

We are experiencing printing problems coming from an Unix host. In Feb. 05 we applied patches to the Unix operating system. Shortly the patches were applied we began experiencing problems printing on a IBM 6400 that emulates an Epson printer. When the printing starts we can print about 10 pages and...

2. UNIX for Advanced & Expert Users

File system problems

Hi All, I am currently running Linux on a file server. The server starts experiencing problems (slow access, no access). After a shutdown and reboot, the file system is corrupted and requires to run fsck to clean up. Is this signs of a failing hard drive? Ken

3. UNIX for Advanced & Expert Users

Problems when rebooting the system

Hi ! I am working on a server. We have ABAQUS installed on it. I added a compiler to .env file and added usr/local...../IMSL/... to the path. Then i restarted the computer and I get this error: when I am doing interactive option (Red hat Lunix OS) Start service local Yes/no/Continue? no...

4. AIX

system command and threads problems

Hi, my name is German. Im working with an aix over one year and i have developed a PRO*C multithread process that reads commands from a table and execute it in parallel (one command by thread) with a system function call, so depending the process exit code (system return value) , I put a mark...

5. UNIX for Dummies Questions & Answers

Posix vs System V IPC quesions

What are the differences/similarities between posix and system V ipc and their mechanisms? also, why is system v only limited to inter-process communication on a single node? thanks

6. Programming

How to Develop a 2 IPC system calls

I need to develop 2 IPC system calls. 1) The first one allows sender to send a message to set of receivers in a single call. 2) The second one allows receiver to receives all message that have been sent to it in a single call Please help me in developing this system calls ....atleast how...

7. Shell Programming and Scripting

Develop 2 IPC System Calls

8. Programming

IPC - queue problems

Hi, I�m having a lot of problems when working with message queues, both on HP-UX Systems and Sun Solaris. When we fill a queue with a messages, the system hangs and locks everything that relies on the use of IPC resources. Anyone knows how to eliminate this problem? Thanks, Haroldo Teixeira

9. 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...

10. Programming

Problems with pipe IPC

I'm currently studying IPC, I have a first program A: Do an exec for B and wait B: Receive through a fifo a string from a third program "C" and have to resend it to A I was thinking to open a pipe in A before the exec, then passing fd to B as an argument if(pipe(fd)==-1){ ...

LEARN ABOUT OSX

ipcs

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