603 lines
22 KiB
HTML
603 lines
22 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<html>
|
|
<head>
|
|
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
|
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
|
<link type="text/css" rel="stylesheet" href="style.css"><!-- Generated by The Open Group's rhtm tool v1.2.1 -->
|
|
<!-- Copyright (c) 2001 The Open Group, All Rights Reserved -->
|
|
<title>ipcs</title>
|
|
</head>
|
|
<body bgcolor="white">
|
|
<script type="text/javascript" language="JavaScript" src="../jscript/codes.js">
|
|
</script>
|
|
|
|
<basefont size="3"> <a name="ipcs"></a> <a name="tag_04_69"></a><!-- ipcs -->
|
|
<!--header start-->
|
|
<center><font size="2">The Open Group Base Specifications Issue 6<br>
|
|
IEEE Std 1003.1-2001<br>
|
|
Copyright © 2001 The IEEE and The Open Group, All Rights reserved.</font></center>
|
|
|
|
<!--header end-->
|
|
<hr size="2" noshade>
|
|
<h4><a name="tag_04_69_01"></a>NAME</h4>
|
|
|
|
<blockquote>ipcs - report XSI interprocess communication facilities status</blockquote>
|
|
|
|
<h4><a name="tag_04_69_02"></a>SYNOPSIS</h4>
|
|
|
|
<blockquote class="synopsis">
|
|
<div class="box"><code><tt><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt=
|
|
"[Option Start]" border="0"> ipcs</tt> <b>[</b><tt>-qms</tt><b>][</b><tt>-a | -bcopt</tt><b>]</b><tt><img src=
|
|
"../images/opt-end.gif" alt="[Option End]" border="0"></tt></code></div>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_03"></a>DESCRIPTION</h4>
|
|
|
|
<blockquote>
|
|
<p>The <i>ipcs</i> utility shall write information about active interprocess communication facilities.</p>
|
|
|
|
<p>Without options, information shall be written in short format for message queues, shared memory segments, and semaphore sets
|
|
that are currently active in the system. Otherwise, the information that is displayed is controlled by the options specified.</p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_04"></a>OPTIONS</h4>
|
|
|
|
<blockquote>
|
|
<p>The <i>ipcs</i> facility supports the Base Definitions volume of IEEE Std 1003.1-2001, <a href=
|
|
"../basedefs/xbd_chap12.html#tag_12_02">Section 12.2, Utility Syntax Guidelines</a>.</p>
|
|
|
|
<p>The <i>ipcs</i> utility accepts the following options:</p>
|
|
|
|
<dl compact>
|
|
<dt><b>-q</b></dt>
|
|
|
|
<dd>Write information about active message queues.</dd>
|
|
|
|
<dt><b>-m</b></dt>
|
|
|
|
<dd>Write information about active shared memory segments.</dd>
|
|
|
|
<dt><b>-s</b></dt>
|
|
|
|
<dd>Write information about active semaphore sets.</dd>
|
|
</dl>
|
|
|
|
<p>If <b>-q</b>, <b>-m</b>, or <b>-s</b> are specified, only information about those facilities shall be written. If none of these
|
|
three are specified, information about all three shall be written subject to the following options:</p>
|
|
|
|
<dl compact>
|
|
<dt><b>-a</b></dt>
|
|
|
|
<dd>Use all print options. (This is a shorthand notation for <b>-b</b>, <b>-c</b>, <b>-o</b>, <b>-p</b>, and <b>-t</b>.)</dd>
|
|
|
|
<dt><b>-b</b></dt>
|
|
|
|
<dd>Write information on maximum allowable size. (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.)</dd>
|
|
|
|
<dt><b>-c</b></dt>
|
|
|
|
<dd>Write creator's user name and group name; see below.</dd>
|
|
|
|
<dt><b>-o</b></dt>
|
|
|
|
<dd>Write information on outstanding usage. (Number of messages on queue and total number of bytes in messages on queue for message
|
|
queues, and number of processes attached to shared memory segments.)</dd>
|
|
|
|
<dt><b>-p</b></dt>
|
|
|
|
<dd>Write process number information. (Process ID of the last process to send a message and process ID of the last process to
|
|
receive a message on message queues, process ID of the creating process, and process ID of the last process to attach or detach on
|
|
shared memory segments.)</dd>
|
|
|
|
<dt><b>-t</b></dt>
|
|
|
|
<dd>Write time information. (Time of the last control operation that changed the access permissions for all facilities, time of the
|
|
last <a href="../functions/msgsnd.html"><i>msgsnd</i>()</a> and <a href="../functions/msgrcv.html"><i>msgrcv</i>()</a> operations
|
|
on message queues, time of the last <a href="../functions/shmat.html"><i>shmat</i>()</a> and <a href=
|
|
"../functions/shmdt.html"><i>shmdt</i>()</a> operations on shared memory, and time of the last <a href=
|
|
"../functions/semop.html"><i>semop</i>()</a> operation on semaphores.)</dd>
|
|
</dl>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_05"></a>OPERANDS</h4>
|
|
|
|
<blockquote>
|
|
<p>None.</p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_06"></a>STDIN</h4>
|
|
|
|
<blockquote>
|
|
<p>Not used.</p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_07"></a>INPUT FILES</h4>
|
|
|
|
<blockquote>
|
|
<ul>
|
|
<li>
|
|
<p>The group database</p>
|
|
</li>
|
|
|
|
<li>
|
|
<p>The user database</p>
|
|
</li>
|
|
</ul>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_08"></a>ENVIRONMENT VARIABLES</h4>
|
|
|
|
<blockquote>
|
|
<p>The following environment variables shall affect the execution of <i>ipcs</i>:</p>
|
|
|
|
<dl compact>
|
|
<dt><i>LANG</i></dt>
|
|
|
|
<dd>Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of
|
|
IEEE Std 1003.1-2001, <a href="../basedefs/xbd_chap08.html#tag_08_02">Section 8.2, Internationalization Variables</a> for
|
|
the precedence of internationalization variables used to determine the values of locale categories.)</dd>
|
|
|
|
<dt><i>LC_ALL</i></dt>
|
|
|
|
<dd>If set to a non-empty string value, override the values of all the other internationalization variables.</dd>
|
|
|
|
<dt><i>LC_CTYPE</i></dt>
|
|
|
|
<dd>Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as
|
|
opposed to multi-byte characters in arguments).</dd>
|
|
|
|
<dt><i>LC_MESSAGES</i></dt>
|
|
|
|
<dd>Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard
|
|
error.</dd>
|
|
|
|
<dt><i>NLSPATH</i></dt>
|
|
|
|
<dd>Determine the location of message catalogs for the processing of <i>LC_MESSAGES .</i></dd>
|
|
|
|
<dt><i>TZ</i></dt>
|
|
|
|
<dd>Determine the timezone for the date and time strings written by <i>ipcs</i>. If <i>TZ</i> is unset or null, an unspecified
|
|
default timezone shall be used.</dd>
|
|
</dl>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_09"></a>ASYNCHRONOUS EVENTS</h4>
|
|
|
|
<blockquote>
|
|
<p>Default.</p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_10"></a>STDOUT</h4>
|
|
|
|
<blockquote>
|
|
<p>An introductory line shall be written with the format:</p>
|
|
|
|
<pre>
|
|
<tt>"IPC status from %s as of %s\n", <</tt><i>source</i><tt>>, <</tt><i>date</i><tt>>
|
|
</tt>
|
|
</pre>
|
|
|
|
<p>where <<i>source</i>> indicates the source used to gather the statistics and <<i>date</i>> is the information that
|
|
would be produced by the <a href="../utilities/date.html"><i>date</i></a> command when invoked in the POSIX locale.</p>
|
|
|
|
<p>The <i>ipcs</i> utility then shall create up to three reports depending upon the <b>-q</b>, <b>-m</b>, and <b>-s</b> options.
|
|
The first report shall indicate the status of message queues, the second report shall indicate the status of shared memory
|
|
segments, and the third report shall indicate the status of semaphore sets.</p>
|
|
|
|
<p>If the corresponding facility is not installed or has not been used since the last reboot, then the report shall be written out
|
|
in the format:</p>
|
|
|
|
<pre>
|
|
<tt>"%s facility not in system.\n", <</tt><i>facility</i><tt>>
|
|
</tt>
|
|
</pre>
|
|
|
|
<p>where <<i>facility</i>> is <i>Message Queue</i>, <i>Shared Memory</i>, or <i>Semaphore</i>, as appropriate. If the
|
|
facility has been installed and has been used since the last reboot, column headings separated by one or more spaces and followed
|
|
by a <newline> shall be written as indicated below followed by the facility name written out using the format:</p>
|
|
|
|
<pre>
|
|
<tt>"%s:\n", <</tt><i>facility</i><tt>>
|
|
</tt>
|
|
</pre>
|
|
|
|
<p>where <<i>facility</i>> is <i>Message Queues</i>, <i>Shared Memory</i>, or <i>Semaphores</i>, as appropriate. On the
|
|
second and third reports the column headings need not be written if the last column headings written already provide column
|
|
headings for all information in that report.</p>
|
|
|
|
<p>The column headings provided in the first column below and the meaning of the information in those columns shall be given in
|
|
order below; the letters in parentheses indicate the options that shall cause the corresponding column to appear; "all" means
|
|
that the column shall always appear. Each column is separated by one or more <space>s. Note that these options only determine
|
|
what information is provided for each report; they do not determine which reports are written.</p>
|
|
|
|
<dl compact>
|
|
<dt>T (all)</dt>
|
|
|
|
<dd>Type of facility:
|
|
|
|
<dl compact>
|
|
<dt><tt>q</tt></dt>
|
|
|
|
<dd>Message queue.</dd>
|
|
|
|
<dt><tt>m</tt></dt>
|
|
|
|
<dd>Shared memory segment.</dd>
|
|
|
|
<dt><tt>s</tt></dt>
|
|
|
|
<dd>Semaphore.</dd>
|
|
</dl>
|
|
|
|
<p>This field is a single character written using the format <tt>%c</tt> .</p>
|
|
</dd>
|
|
|
|
<dt>ID (all)</dt>
|
|
|
|
<dd>The identifier for the facility entry. This field shall be written using the format <tt>%d</tt> .</dd>
|
|
|
|
<dt>KEY (all)</dt>
|
|
|
|
<dd>The key used as an argument to <a href="../functions/msgget.html"><i>msgget</i>()</a>, <a href=
|
|
"../functions/semget.html"><i>semget</i>()</a>, or <a href="../functions/shmget.html"><i>shmget</i>()</a> to create the facility
|
|
entry. <basefont size="2">
|
|
|
|
<dl>
|
|
<dt><b>Note:</b></dt>
|
|
|
|
<dd>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.</dd>
|
|
</dl>
|
|
|
|
<basefont size="3"> This field shall be written using the format <tt>0x%x</tt>.</dd>
|
|
|
|
<dt>MODE (all)</dt>
|
|
|
|
<dd>The facility access modes and flags. The mode shall consist of 11 characters that are interpreted as follows.
|
|
|
|
<p>The first character shall be:</p>
|
|
|
|
<dl compact>
|
|
<dt><tt>S</tt></dt>
|
|
|
|
<dd>If a process is waiting on a <a href="../functions/msgsnd.html"><i>msgsnd</i>()</a> operation.</dd>
|
|
|
|
<dt><tt>-</tt></dt>
|
|
|
|
<dd>If the above is not true.</dd>
|
|
</dl>
|
|
|
|
<p>The second character shall be:</p>
|
|
|
|
<dl compact>
|
|
<dt><tt>R</tt></dt>
|
|
|
|
<dd>If a process is waiting on a <a href="../functions/msgrcv.html"><i>msgrcv</i>()</a> operation.</dd>
|
|
|
|
<dt><tt>C</tt> or <tt>-</tt></dt>
|
|
|
|
<dd>If the associated shared memory segment is to be cleared when the first attach operation is executed.</dd>
|
|
|
|
<dt><tt>-</tt></dt>
|
|
|
|
<dd>If none of the above is true.</dd>
|
|
</dl>
|
|
|
|
<p>The next nine characters shall be 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 usergroup of the facility entry; and the last to all others. Within each set, the first
|
|
character indicates permission to read, the second character indicates permission to write or alter the facility entry, and the
|
|
last character is a minus sign ( <tt>'-'</tt> ).</p>
|
|
|
|
<p>The permissions shall be indicated as follows:</p>
|
|
|
|
<dl compact>
|
|
<dt><i>r</i></dt>
|
|
|
|
<dd>If read permission is granted.</dd>
|
|
|
|
<dt><i>w</i></dt>
|
|
|
|
<dd>If write permission is granted.</dd>
|
|
|
|
<dt><i>a</i></dt>
|
|
|
|
<dd>If alter permission is granted.</dd>
|
|
|
|
<dt><tt>-</tt></dt>
|
|
|
|
<dd>If the indicated permission is not granted.</dd>
|
|
</dl>
|
|
|
|
<p>The first character following the permissions specifies if there is an alternate or additional access control method associated
|
|
with the facility. If there is no alternate or additional access control method associated with the facility, a single
|
|
<space> shall be written; otherwise, another printable character is written.</p>
|
|
</dd>
|
|
|
|
<dt>OWNER (all)</dt>
|
|
|
|
<dd>The user name of the owner of the facility entry. If the user name of the owner is found in the user database, at least the
|
|
first eight column positions of the name shall be written using the format <tt>%s</tt> . Otherwise, the user ID of the owner shall
|
|
be written using the format <tt>%d</tt> .</dd>
|
|
|
|
<dt>GROUP (all)</dt>
|
|
|
|
<dd>The group name of the owner of the facility entry. If the group name of the owner is found in the group database, at least the
|
|
first eight column positions of the name shall be written using the format <tt>%s</tt> . Otherwise, the group ID of the owner shall
|
|
be written using the format <tt>%d</tt> .</dd>
|
|
</dl>
|
|
|
|
<p>The following nine columns shall be only written out for message queues:</p>
|
|
|
|
<dl compact>
|
|
<dt>CREATOR (<b>a</b>,<b>c</b>)</dt>
|
|
|
|
<dd>The user name of the creator of the facility entry. If the user name of the creator is found in the user database, at least the
|
|
first eight column positions of the name shall be written using the format <tt>%s</tt> . Otherwise, the user ID of the creator
|
|
shall be written using the format <tt>%d</tt> .</dd>
|
|
|
|
<dt>CGROUP (<b>a</b>,<b>c</b>)</dt>
|
|
|
|
<dd>The group name of the creator of the facility entry. If the group name of the creator is found in the group database, at least
|
|
the first eight column positions of the name shall be written using the format <tt>%s</tt> . Otherwise, the group ID of the creator
|
|
shall be written using the format <tt>%d</tt> .</dd>
|
|
|
|
<dt>CBYTES (<b>a</b>,<b>o</b>)</dt>
|
|
|
|
<dd>The number of bytes in messages currently outstanding on the associated message queue. This field shall be written using the
|
|
format <tt>%d</tt> .</dd>
|
|
|
|
<dt>QNUM (<b>a</b>,<b>o</b>)</dt>
|
|
|
|
<dd>The number of messages currently outstanding on the associated message queue. This field shall be written using the format
|
|
<tt>%d</tt> .</dd>
|
|
|
|
<dt>QBYTES (<b>a</b>,<b>b</b>)</dt>
|
|
|
|
<dd>The maximum number of bytes allowed in messages outstanding on the associated message queue. This field shall be written using
|
|
the format <tt>%d</tt> .</dd>
|
|
|
|
<dt>LSPID (<b>a</b>,<b>p</b>)</dt>
|
|
|
|
<dd>The process ID of the last process to send a message to the associated queue. This field shall be written using the format:
|
|
|
|
<pre>
|
|
<tt>"%d", <</tt><i>pid</i><tt>>
|
|
</tt>
|
|
</pre>
|
|
|
|
<p>where <<i>pid</i>> is 0 if no message has been sent to the corresponding message queue; otherwise, <<i>pid</i>>
|
|
shall be the process ID of the last process to send a message to the queue.</p>
|
|
</dd>
|
|
|
|
<dt>LRPID (<b>a</b>,<b>p</b>)</dt>
|
|
|
|
<dd>The process ID of the last process to receive a message from the associated queue. This field shall be written using the
|
|
format:
|
|
|
|
<pre>
|
|
<tt>"%d", <</tt><i>pid</i><tt>>
|
|
</tt>
|
|
</pre>
|
|
|
|
<p>where <<i>pid</i>> is 0 if no message has been received from the corresponding message queue; otherwise,
|
|
<<i>pid</i>> shall be the process ID of the last process to receive a message from the queue.</p>
|
|
</dd>
|
|
|
|
<dt>STIME (<b>a</b>,<b>t</b>)</dt>
|
|
|
|
<dd>The time the last message was sent to the associated queue. If a message has been sent to the corresponding message queue, the
|
|
hour, minute, and second of the last time a message was sent to the queue shall be written using the format <tt>%d</tt> :
|
|
<tt>%2.2d</tt> : <tt>%2.2d</tt> . Otherwise, the format <tt>" no-entry"</tt> shall be written.</dd>
|
|
|
|
<dt>RTIME (<b>a</b>,<b>t</b>)</dt>
|
|
|
|
<dd>The time the last message was received from the associated queue. If a message has been received from the corresponding message
|
|
queue, the hour, minute, and second of the last time a message was received from the queue shall be written using the format
|
|
<tt>%d</tt> : <tt>%2.2d</tt> : <tt>%2.2d</tt> . Otherwise, the format <tt>" no-entry"</tt> shall be written.</dd>
|
|
</dl>
|
|
|
|
<p>The following eight columns shall be only written out for shared memory segments.</p>
|
|
|
|
<dl compact>
|
|
<dt>CREATOR (<b>a</b>,<b>c</b>)</dt>
|
|
|
|
<dd>The user of the creator of the facility entry. If the user name of the creator is found in the user database, at least the
|
|
first eight column positions of the name shall be written using the format <tt>%s</tt> . Otherwise, the user ID of the creator
|
|
shall be written using the format <tt>%d</tt> .</dd>
|
|
|
|
<dt>CGROUP (<b>a</b>,<b>c</b>)</dt>
|
|
|
|
<dd>The group name of the creator of the facility entry. If the group name of the creator is found in the group database, at least
|
|
the first eight column positions of the name shall be written using the format <tt>%s</tt> . Otherwise, the group ID of the creator
|
|
shall be written using the format <tt>%d</tt> .</dd>
|
|
|
|
<dt>NATTCH (<b>a</b>,<b>o</b>)</dt>
|
|
|
|
<dd>The number of processes attached to the associated shared memory segment. This field shall be written using the format
|
|
<tt>%d</tt> .</dd>
|
|
|
|
<dt>SEGSZ (<b>a</b>,<b>b</b>)</dt>
|
|
|
|
<dd>The size of the associated shared memory segment. This field shall be written using the format <tt>%d</tt> .</dd>
|
|
|
|
<dt>CPID (<b>a</b>,<b>p</b>)</dt>
|
|
|
|
<dd>The process ID of the creator of the shared memory entry. This field shall be written using the format <tt>%d</tt> .</dd>
|
|
|
|
<dt>LPID (<b>a</b>,<b>p</b>)</dt>
|
|
|
|
<dd>The process ID of the last process to attach or detach the shared memory segment. This field shall be written using the format:
|
|
|
|
|
|
<pre>
|
|
<tt>"%d", <</tt><i>pid</i><tt>>
|
|
</tt>
|
|
</pre>
|
|
|
|
<p>where <<i>pid</i>> is 0 if no process has attached the corresponding shared memory segment; otherwise, <<i>pid</i>>
|
|
shall be the process ID of the last process to attach or detach the segment.</p>
|
|
</dd>
|
|
|
|
<dt>ATIME (<b>a</b>,<b>t</b>)</dt>
|
|
|
|
<dd>The time the last attach on the associated shared memory segment was completed. If the corresponding shared memory segment has
|
|
ever been attached, the hour, minute, and second of the last time the segment was attached shall be written using the format
|
|
<tt>%d</tt> : <tt>%2.2d</tt> : <tt>%2.2d</tt> . Otherwise, the format <tt>" no-entry"</tt> shall be written.</dd>
|
|
|
|
<dt>DTIME (<b>a</b>,<b>t</b>)</dt>
|
|
|
|
<dd>The time the last detach on the associated shared memory segment was completed. If the corresponding shared memory segment has
|
|
ever been detached, the hour, minute, and second of the last time the segment was detached shall be written using the format
|
|
<tt>%d</tt> : <tt>%2.2d</tt> : <tt>%2.2d</tt> . Otherwise, the format <tt>" no-entry"</tt> shall be written.</dd>
|
|
</dl>
|
|
|
|
<p>The following four columns shall be only written out for semaphore sets:</p>
|
|
|
|
<dl compact>
|
|
<dt>CREATOR (<b>a</b>,<b>c</b>)</dt>
|
|
|
|
<dd>The user of the creator of the facility entry. If the user name of the creator is found in the user database, at least the
|
|
first eight column positions of the name shall be written using the format <tt>%s</tt> . Otherwise, the user ID of the creator
|
|
shall be written using the format <tt>%d</tt> .</dd>
|
|
|
|
<dt>CGROUP (<b>a</b>,<b>c</b>)</dt>
|
|
|
|
<dd>The group name of the creator of the facility entry. If the group name of the creator is found in the group database, at least
|
|
the first eight column positions of the name shall be written using the format <tt>%s</tt> . Otherwise, the group ID of the creator
|
|
shall be written using the format <tt>%d</tt> .</dd>
|
|
|
|
<dt>NSEMS (<b>a</b>,<b>b</b>)</dt>
|
|
|
|
<dd>The number of semaphores in the set associated with the semaphore entry. This field shall be written using the format
|
|
<tt>%d</tt> .</dd>
|
|
|
|
<dt>OTIME (<b>a</b>,<b>t</b>)</dt>
|
|
|
|
<dd>The time the last semaphore operation on the set associated with the semaphore entry was completed. If a semaphore operation
|
|
has ever been performed on the corresponding semaphore set, the hour, minute, and second of the last semaphore operation on the
|
|
semaphore set shall be written using the format <tt>%d</tt> : <tt>%2.2d</tt> : <tt>%2.2d</tt> . Otherwise, the format
|
|
<tt>" no-entry"</tt> shall be written.</dd>
|
|
</dl>
|
|
|
|
<p>The following column shall be written for all three reports when it is requested:</p>
|
|
|
|
<dl compact>
|
|
<dt>CTIME (<b>a</b>,<b>t</b>)</dt>
|
|
|
|
<dd>The time the associated entry was created or changed. The hour, minute, and second of the time when the associated entry was
|
|
created shall be written using the format <tt>%d</tt> : <tt>%2.2d</tt> : <tt>%2.2d</tt> .</dd>
|
|
</dl>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_11"></a>STDERR</h4>
|
|
|
|
<blockquote>
|
|
<p>The standard error shall be used only for diagnostic messages.</p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_12"></a>OUTPUT FILES</h4>
|
|
|
|
<blockquote>
|
|
<p>None.</p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_13"></a>EXTENDED DESCRIPTION</h4>
|
|
|
|
<blockquote>
|
|
<p>None.</p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_14"></a>EXIT STATUS</h4>
|
|
|
|
<blockquote>
|
|
<p>The following exit values shall be returned:</p>
|
|
|
|
<dl compact>
|
|
<dt> 0</dt>
|
|
|
|
<dd>Successful completion.</dd>
|
|
|
|
<dt>>0</dt>
|
|
|
|
<dd>An error occurred.</dd>
|
|
</dl>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_15"></a>CONSEQUENCES OF ERRORS</h4>
|
|
|
|
<blockquote>
|
|
<p>Default.</p>
|
|
</blockquote>
|
|
|
|
<hr>
|
|
<div class="box"><em>The following sections are informative.</em></div>
|
|
|
|
<h4><a name="tag_04_69_16"></a>APPLICATION USAGE</h4>
|
|
|
|
<blockquote>
|
|
<p>Things can change while <i>ipcs</i> is running; the information it gives is guaranteed to be accurate only when it was
|
|
retrieved.</p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_17"></a>EXAMPLES</h4>
|
|
|
|
<blockquote>
|
|
<p>None.</p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_18"></a>RATIONALE</h4>
|
|
|
|
<blockquote>
|
|
<p>None.</p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_19"></a>FUTURE DIRECTIONS</h4>
|
|
|
|
<blockquote>
|
|
<p>None.</p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_20"></a>SEE ALSO</h4>
|
|
|
|
<blockquote>
|
|
<p>The System Interfaces volume of IEEE Std 1003.1-2001, <a href="../functions/msgrcv.html"><i>msgrcv</i>()</a>, <a href=
|
|
"../functions/msgsnd.html"><i>msgsnd</i>()</a>, <a href="../functions/semget.html"><i>semget</i>()</a>, <a href=
|
|
"../functions/semop.html"><i>semop</i>()</a>, <a href="../functions/shmat.html"><i>shmat</i>()</a>, <a href=
|
|
"../functions/shmdt.html"><i>shmdt</i>()</a>, <a href="../functions/shmget.html"><i>shmget</i>()</a></p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_21"></a>CHANGE HISTORY</h4>
|
|
|
|
<blockquote>
|
|
<p>First released in Issue 5.</p>
|
|
</blockquote>
|
|
|
|
<h4><a name="tag_04_69_22"></a>Issue 6</h4>
|
|
|
|
<blockquote>
|
|
<p>The Open Group Corrigendum U020/1 is applied, correcting the SYNOPSIS.</p>
|
|
|
|
<p>The Open Group Corrigenda U032/1 and U032/2 are applied, clarifying the output format.</p>
|
|
|
|
<p>The Open Group Base Resolution bwg98-004 is applied.</p>
|
|
</blockquote>
|
|
|
|
<div class="box"><em>End of informative text.</em></div>
|
|
|
|
<hr>
|
|
<hr size="2" noshade>
|
|
<center><font size="2"><!--footer start-->
|
|
UNIX ® is a registered Trademark of The Open Group.<br>
|
|
POSIX ® is a registered Trademark of The IEEE.<br>
|
|
[ <a href="../mindex.html">Main Index</a> | <a href="../basedefs/contents.html">XBD</a> | <a href=
|
|
"../utilities/contents.html">XCU</a> | <a href="../functions/contents.html">XSH</a> | <a href="../xrat/contents.html">XRAT</a>
|
|
]</font></center>
|
|
|
|
<!--footer end-->
|
|
<hr size="2" noshade>
|
|
</body>
|
|
</html>
|
|
|