summaryrefslogtreecommitdiffstats
path: root/man/sd_bus_get_n_queued_read.xml
blob: f949c936c21403432eadc29c361921ce666cbf10 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
<?xml version='1.0'?>
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!-- SPDX-License-Identifier: LGPL-2.1+ -->

<refentry id="sd_bus_get_n_queued_read">

  <refentryinfo>
    <title>sd_bus_get_fd</title>
    <productname>systemd</productname>
  </refentryinfo>

  <refmeta>
    <refentrytitle>sd_bus_get_n_queued_read</refentrytitle>
    <manvolnum>3</manvolnum>
  </refmeta>

  <refnamediv>
    <refname>sd_bus_get_n_queued_read</refname>
    <refname>sd_bus_get_n_queued_write</refname>

    <refpurpose>Get the number of pending bus messages in the read and write queues of a bus connection object</refpurpose>
  </refnamediv>

  <refsynopsisdiv>
    <funcsynopsis>
      <funcsynopsisinfo>#include &lt;systemd/sd-bus.h&gt;</funcsynopsisinfo>

      <funcprototype>
        <funcdef>int <function>sd_bus_get_n_queued_read</function></funcdef>
        <paramdef>sd_bus *<parameter>bus</parameter></paramdef>
        <paramdef>uint64_t *<parameter>ret</parameter></paramdef>
      </funcprototype>

      <funcprototype>
        <funcdef>int <function>sd_bus_get_n_queued_write</function></funcdef>
        <paramdef>sd_bus *<parameter>bus</parameter></paramdef>
        <paramdef>uint64_t *<parameter>ret</parameter></paramdef>
      </funcprototype>
    </funcsynopsis>
  </refsynopsisdiv>

  <refsect1>
    <title>Description</title>

    <para>
      <function>sd_bus_get_n_queued_read()</function> may be used to query the number of bus messages in the read queue
      of a bus connection object. The read queue contains all messages read from the transport medium (e.g. network
      socket) but not yet processed locally. The function expects two arguments: the bus object to query, and a pointer
      to a 64bit counter variable to write the current queue size to. Use <function>sd_bus_process()</function> in
      order to process queued messages, i.e. to reduce the size of the read queue (as well as, in fact, the write
      queue, see below).
    </para>

    <para>
      Similarly, <function>sd_bus_get_n_queued_write()</function> may be used to query the number of currently pending
      bus messages in the write queue of a bus connection object. The write queue contains all messages enqueued into
      the connection with a call such as <function>sd_bus_send()</function> but not yet written to the transport
      medium. The expected arguments are similar to <function>sd_bus_get_n_queued_read()</function>. Here too, use
      <function>sd_bus_process()</function> to reduce the size of the write queue. Alternatively, use
      <function>sd_bus_flush()</function> to synchronously write out any pending bus messages until the write queue is
      empty.
    </para>
  </refsect1>

  <refsect1>
    <title>Return Value</title>

    <para>On success, these functions return 0 or a positive integer. On failure, they return a negative errno-style
    error code.</para>

    <refsect2>
      <title>Errors</title>

      <para>Returned errors may indicate the following problems:</para>

      <variablelist>
        <varlistentry>
          <term><constant>-ECHILD</constant></term>

          <listitem><para>The bus connection was created in a different process.</para></listitem>
        </varlistentry>

      </variablelist>
    </refsect2>
  </refsect1>

  <refsect1>
    <title>See Also</title>

    <para>
      <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
      <citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
      <citerefentry><refentrytitle>sd_bus_process</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
      <citerefentry><refentrytitle>sd_bus_send</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
      <citerefentry><refentrytitle>sd_bus_flush</refentrytitle><manvolnum>3</manvolnum></citerefentry>
    </para>
  </refsect1>

</refentry>