Skip to content

Commit

Permalink
Add receptorctl work results doc (#1064)
Browse files Browse the repository at this point in the history
  • Loading branch information
thom-at-redhat authored Jun 14, 2024
1 parent 9753cfb commit ef41510
Show file tree
Hide file tree
Showing 2 changed files with 27 additions and 0 deletions.
1 change: 1 addition & 0 deletions docs/source/receptorctl/receptorctl_index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -18,3 +18,4 @@ The Receptor client, ``receptorctl``, provides a command line interface for inte
receptorctl_work_cancel
receptorctl_work_list
receptorctl_work_release
receptorctl_work_results
26 changes: 26 additions & 0 deletions docs/source/receptorctl/receptorctl_work_results.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
------------
work results
------------

.. contents::
:local:

``receptorctl work results`` gets results for successfully completed, failed, stopped, or currently running, units of work.

Command syntax: ``receptorctl --socket=<socket_path> work results [<<Options>>] <<Unit ID>> [...]``

``socket_path`` is the control socket address for the Receptor connection.
The default is ``unix:`` for a Unix socket.
Use ``tcp://`` for a TCP socket.
The corresponding environment variable is ``RECEPTORCTL_SOCKET``.

.. code-block:: text
ss --listening --processes --unix 'src = unix:<socket_path>'
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
u_str LISTEN 0 4096 /tmp/local.sock 38130170 * 0 users:(("receptor",pid=3226769,fd=7))
``ps -fp $(pidof receptor)``
``lsof -p <pid>``

``Unit ID`` is a unique identifier for a work unit (job). When running the ``work results`` command, you should specify the ``Unit ID`` for the Receptor node to which you are connected.

0 comments on commit ef41510

Please sign in to comment.