ipcs.html

IEEE 1003.1-2003, Single Unix Specification v3

<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
&lt;space&gt; 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", &lt;</tt><i>pid</i><tt>&gt;
</tt>
</pre>

<p>where &lt;<i>pid</i>&gt; is 0 if no message has been sent to the corresponding message queue; otherwise, &lt;<i>pid</i>&gt;
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", &lt;</tt><i>pid</i><tt>&gt;
</tt>
</pre>

<p>where &lt;<i>pid</i>&gt; is 0 if no message has been received from the corresponding message queue; otherwise,
&lt;<i>pid</i>&gt; 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>"&nbsp;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>"&nbsp;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", &lt;</tt><i>pid</i><tt>&gt;
</tt>
</pre>

<p>where &lt;<i>pid</i>&gt; is 0 if no process has attached the corresponding shared memory segment; otherwise, &lt;<i>pid</i>&gt;
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>"&nbsp;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>"&nbsp;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>"&nbsp;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>&nbsp;0</dt>

<dd>Successful completion.</dd>

<dt>&gt;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&nbsp;Std&nbsp;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 &reg; is a registered Trademark of The Open Group.<br>
POSIX &reg; 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>