Home
last modified time | relevance | path

Searched full:clients (Results 1 – 25 of 355) sorted by relevance

12345678910>>...15

/openbmc/phosphor-snmp/test/
H A Dtest_snmp_conf_manager.cpp49 return manager.clients; in getSNMPClients()
54 for (const auto& val : manager.clients) in isClientExist()
67 for (const auto& val : manager.clients) in deleteSNMPClient()
77 if (manager.clients.contains(id)) in deleteSNMPClient()
79 manager.clients.at(id)->delete_(); in deleteSNMPClient()
96 auto& clients = getSNMPClients(); in TEST_F() local
97 EXPECT_EQ(1U, clients.size()); in TEST_F()
104 // add multiple clients and check whether the object path is generated in TEST_F()
113 // check both the clients get created in TEST_F()
114 auto& clients = getSNMPClients(); in TEST_F() local
[all …]
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/krb5/krb5/
H A D0002-Avoid-strict-prototype-compiler-errors.patch21 src/clients/kcpytkt/kcpytkt.c | 2 +-
22 src/clients/kdeltkt/kdeltkt.c | 2 +-
23 src/clients/kinit/kinit.c | 4 ++--
24 src/clients/kinit/kinit_kdb.c | 2 +-
25 src/clients/klist/klist.c | 4 ++--
44 diff --git a/src/clients/kcpytkt/kcpytkt.c b/src/clients/kcpytkt/kcpytkt.c
46 --- a/src/clients/kcpytkt/kcpytkt.c
47 +++ b/src/clients/kcpytkt/kcpytkt.c
57 diff --git a/src/clients/kdeltkt/kdeltkt.c b/src/clients/kdeltkt/kdeltkt.c
59 --- a/src/clients/kdeltkt/kdeltkt.c
[all …]
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/libmemcached/files/
H A D0001-Fix-comparison-types.patch13 clients/memflush.cc | 4 ++--
16 diff --git a/clients/memflush.cc b/clients/memflush.cc
18 --- a/clients/memflush.cc
19 +++ b/clients/memflush.cc
/openbmc/obmc-console/
H A Dsocket-handler.c54 struct client **clients; member
83 if (sh->clients[idx] == client) { in client_close()
99 memmove(&sh->clients[idx], &sh->clients[idx + 1], in client_close()
100 sizeof(*sh->clients) * (sh->n_clients - idx)); in client_close()
102 free(sh->clients); in client_close()
103 sh->clients = NULL; in client_close()
105 sh->clients = reallocarray(sh->clients, sh->n_clients, in client_close()
106 sizeof(*sh->clients)); in client_close()
345 sh->clients = in socket_poll()
346 reallocarray(sh->clients, sh->n_clients, sizeof(*sh->clients)); in socket_poll()
[all …]
/openbmc/qemu/tests/qemu-iotests/tests/
H A Dnbd-multiconn115 clients = [nbd.NBD() for _ in range(3)]
116 for c in clients:
120 initial_data = clients[0].pread(1024 * 1024, 0)
124 clients[1].pwrite(updated_data, 0)
125 clients[2].flush()
126 current_data = clients[0].pread(1024 * 1024, 0)
131 clients[i].shutdown()
/openbmc/qemu/docs/system/
H A Dtls.rst29 clients on a private intranet, there is no need to use a commercial
35 server and exposing it directly to remote browser clients. In such a
75 should be copied to all servers and clients wishing to utilize TLS
89 clients when connecting. The hostname / IP address that the client
96 permanently assigned IP address(es), and clients are likely to use them
100 for validation is now deprecated. Instead modern TLS clients will
185 The subject alt name extension data is not required for clients, so
189 clients are not in fact HTTP clients, setting this key purpose is still
246 used for network services and clients. It requires specifying the
270 should be performed. This defaults to enabled, meaning clients will
[all …]
/openbmc/phosphor-snmp/
H A Dsnmp_conf_manager.cpp63 this->clients.emplace(lastClientId, std::move(client)); in client()
77 for (const auto& val : clients) in checkClientConfigured()
94 auto it = clients.find(id); in deleteSNMPClient()
95 if (it == clients.end()) in deleteSNMPClient()
119 this->clients.erase(it); in deleteSNMPClient()
148 this->clients.emplace(idNum, std::move(manager)); in restoreClients()
/openbmc/qemu/docs/specs/
H A Divshmem-spec.rst145 - sends connect notifications for the new client to the other clients
147 - sends connect notifications for the other clients to the new client,
155 notifications to the other clients.
160 its connected clients, the clients can elect to continue. They can
162 notification on disconnect, and no new clients can connect. There is
163 no way for the clients to connect to a restarted server. The device
167 production. It assumes all clients use the same number of interrupt
192 2. The client's ID. This is unique among all clients of this server.
199 4. Connect notifications for existing other clients, if any. This is
/openbmc/bmcweb/docs/
H A DCLIENTS.md4 tests and clients that could target it. The below attempts to provide a
5 non-exhaustive list of tests and clients that bmcweb is expected to be
8 specification. Entries in the clients category are intended to host user-facing
46 ## Clients section in Client overview
H A DOEM_SCHEMAS.md22 large amount of reuse, as clients must implement machine-specific APIs, some of
24 also has very little visibility into clients that might interface with Redfish,
32 a breaking change to an external API, given that clients are likely to be
94 To avoid versioning complications with clients, schemas within the OpenBMC
/openbmc/libmctp/utils/
H A Dmctp-demux-daemon.c75 struct client *clients; member
98 struct client *client = &ctx->clients[i]; in client_remove_inactive()
104 memmove(&ctx->clients[i], &ctx->clients[i + 1], in client_remove_inactive()
105 (ctx->n_clients - i) * sizeof(*ctx->clients)); in client_remove_inactive()
106 ctx->clients = realloc(ctx->clients, in client_remove_inactive()
107 ctx->n_clients * sizeof(*ctx->clients)); in client_remove_inactive()
140 struct client *client = &ctx->clients[i]; in rx_message()
336 ctx->clients = in socket_process()
337 realloc(ctx->clients, ctx->n_clients * sizeof(struct client)); in socket_process()
339 client = &ctx->clients[ctx->n_clients - 1]; in socket_process()
[all …]
/openbmc/qemu/include/qemu/
H A Dfifo8.h18 * Create a FIFO of the specified capacity. Clients should call fifo8_destroy()
38 * Clients are responsible for checking for fullness using fifo8_is_full().
49 * Clients are responsible for checking the space left in the FIFO using
59 * Clients are responsible for checking for emptyness using fifo8_is_empty().
69 * Peek the data byte at the current head of the FIFO. Clients are responsible
125 * Clients are responsible for checking the availability of requested data
152 * Clients are responsible for checking the availability of requested data
H A Dfifo32.h29 * Create a FIFO of the specified size. Clients should call fifo32_destroy()
85 * is full. Clients are responsible for checking for fullness using
106 * is full. Clients are responsible for checking the space left in the FIFO
125 * is empty. Clients are responsible for checking for emptiness using
/openbmc/openbmc/meta-raspberrypi/recipes-graphics/wayland/
H A Dweston_%.bbappend1 …:remove:rpi = "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', 'fbdev', 'egl clients', d)}"
5 --disable-simple-egl-clients \
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/
H A Dlibxres_1.2.2.bb5 for X clients to see and monitor the X resource usage of various clients \
/openbmc/openbmc/poky/meta/recipes-graphics/wayland/
H A Dweston_14.0.1.bb36 PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 'kms wayland egl clients', ''…
76 # Clients support
77 PACKAGECONFIG[clients] = "-Dsimple-clients=${SIMPLECLIENTS} -Ddemo-clients=true,-Dsimple-clients= -…
H A Dwayland_1.23.1.bb1 SUMMARY = "Wayland, a protocol between a compositor and clients"
2 DESCRIPTION = "Wayland is a protocol for a compositor to talk to its clients \
5 input devices, an X application, or a wayland client itself. The clients can \
/openbmc/qemu/net/can/
H A Dcan_core.c75 QTAILQ_HEAD(, CanBusClientState) clients;
82 QTAILQ_INIT(&bus->clients); in can_bus_instance_init()
88 QTAILQ_INSERT_TAIL(&bus->clients, client, next); in can_bus_insert_client()
99 QTAILQ_REMOVE(&bus->clients, client, next); in can_bus_remove_client()
114 QTAILQ_FOREACH(peer, &bus->clients, next) { in can_bus_client_send()
/openbmc/docs/designs/
H A Dsol-sysrq.md38 could be connected by multiple clients, using unix domain socket.
41 sequence `\n~B` is used to send the "break signal" between clients and
88 An alternative way to send the "break signal" between clients and console-server
99 clients, which is more work than the state machine solution.
/openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-extended/lcdproc/
H A Dlcdproc_git.bb42 install -D -m 0755 clients/lcdproc/lcdproc ${D}${bindir}/lcdproc
56 install -m 0644 ${S}/clients/lcdproc/lcdproc.conf ${D}${sysconfdir}/lcdproc.conf
64 install -D -m 0755 clients/lcdvc/lcdvc ${D}${sbindir}/lcdvc
67 install -D -m 0644 ${S}/clients/lcdvc/lcdvc.conf ${D}${sysconfdir}/lcdvc.conf
/openbmc/qemu/contrib/ivshmem-server/
H A Divshmem-server.h14 * mode. The ivshmem clients (qemu or ivshmem-client) connect to this
17 * clients using the SCM_RIGHTS cmsg message. Therefore, each client is
45 * vectors are advertised to all connected clients through the connected
106 * Close connections to all clients, close the unix socket and the
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/mdns/mdns/
H A D0002-make-Set-libdns_sd.so-soname-correctly.patch24 Clients: setup ../Clients/build/dns-sd
/openbmc/qemu/docs/interop/
H A Dqmp-spec.rst139 is recommended for clients that accept capability ``oob``.
159 so that requests and responses can match. Clients should drop all the
193 - The ``desc`` member is a human-readable error message. Clients should
343 Clients should use the ``qmp_capabilities`` command to enable capabilities
356 capabilities array (in the `Server Greeting`_). Thus, Clients can check
362 strictness of the Server catches wrong assumptions of Clients about
363 the Server's schema. Clients can assume that, when such validation
367 However, Clients must not assume any particular:
371 new keys and Clients should be able to ignore them
/openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libnet/
H A Dlibnet-ssleay-perl_1.85.bb5 clients, and finally access to the SSL api of SSLeay/OpenSSL package \
6 so you can write servers or clients for more complicated applications."
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DRegisteredClient.v1_1_2.json118 …ent. It is designed to allow well-behaved clients to register with a Redfish service such that ot…
119 …l, register. Clients and management tools that live for long periods of time can create `Register…
193 …all contain the date and time when the client entry expires. Registered clients that are actively…
213 …y of resources that the registered client monitors or configures. Other clients can use this prop…

12345678910>>...15