Home
last modified time | relevance | path

Searched refs:clients (Results 1 – 25 of 277) sorted by relevance

12345678910>>...12

/netbsd/src/external/bsd/tmux/dist/
Dcontrol-notify.c34 TAILQ_FOREACH(c, &clients, entry) { in control_notify_pane_mode_changed()
54 TAILQ_FOREACH(c, &clients, entry) { in control_notify_window_layout_changed()
84 TAILQ_FOREACH(c, &clients, entry) { in control_notify_window_pane_changed()
99 TAILQ_FOREACH(c, &clients, entry) { in control_notify_window_unlinked()
117 TAILQ_FOREACH(c, &clients, entry) { in control_notify_window_linked()
135 TAILQ_FOREACH(c, &clients, entry) { in control_notify_window_renamed()
160 TAILQ_FOREACH(c, &clients, entry) { in control_notify_client_session_changed()
179 TAILQ_FOREACH(c, &clients, entry) { in control_notify_client_detached()
190 TAILQ_FOREACH(c, &clients, entry) { in control_notify_session_renamed()
203 TAILQ_FOREACH(c, &clients, entry) { in control_notify_session_created()
[all …]
Dserver.c42 struct clients clients; variable
211 TAILQ_INIT(&clients); in server_start()
270 TAILQ_FOREACH(c, &clients, entry) { in server_loop()
286 TAILQ_FOREACH(c, &clients, entry) { in server_loop()
296 if (!TAILQ_EMPTY(&clients)) in server_loop()
314 TAILQ_FOREACH_SAFE(c, &clients, entry, c1) { in server_send_exit()
Dserver-fn.c49 TAILQ_FOREACH(c, &clients, entry) { in server_redraw_session()
73 TAILQ_FOREACH(c, &clients, entry) { in server_status_session()
97 TAILQ_FOREACH(c, &clients, entry) { in server_redraw_window()
108 TAILQ_FOREACH(c, &clients, entry) { in server_redraw_window_borders()
136 TAILQ_FOREACH(c, &clients, entry) { in server_lock()
147 TAILQ_FOREACH(c, &clients, entry) { in server_lock_session()
443 TAILQ_FOREACH(c, &clients, entry) { in server_destroy_session()
Dresize.c82 TAILQ_FOREACH (loop, &clients, entry) { in ignore_client_size()
104 TAILQ_FOREACH(loop, &clients, entry) { in clients_with_window()
152 TAILQ_FOREACH(loop, &clients, entry) { in clients_calculate_size()
223 TAILQ_FOREACH(loop, &clients, entry) { in clients_calculate_size()
452 TAILQ_FOREACH(c, &clients, entry) { in recalculate_sizes_now()
Dcmd-detach-client.c81 TAILQ_FOREACH(loop, &clients, entry) { in cmd_detach_client_exec()
93 TAILQ_FOREACH(loop, &clients, entry) { in cmd_detach_client_exec()
Dserver-acl.c133 TAILQ_FOREACH(c, &clients, entry) { in server_acl_user_allow_write()
152 TAILQ_FOREACH(c, &clients, entry) { in server_acl_user_deny_write()
Dcmd-attach-session.c119 TAILQ_FOREACH(c_loop, &clients, entry) { in cmd_attach_session()
143 TAILQ_FOREACH(c_loop, &clients, entry) { in cmd_attach_session()
/netbsd/src/external/bsd/ntp/dist/
DREADME.leapsmear26 NTP servers also pass a leap second warning flag down to their clients via
27 the normal NTP packet exchange, so clients also become aware of an
60 Thus it is not required to use a smearing NTP server for Windows clients,
69 sent to its clients, so that after some predefined interval the leap second
71 e.g. several hours, so that NTP clients can easily follow the clock drift
79 With this approach the time an NTP server sends to its clients still matches
86 Of course, clients which receive the "smeared" time from an NTP server don't
88 just transparent to the clients, and the clients don't even notice there's a
159 NTP clients can follow the smeared time it doesn't matter at all which
163 Since all clients follow the same smeared time the time difference between
[all …]
/netbsd/src/crypto/external/bsd/heimdal/dist/lib/ipc/
Dserver.c485 static struct client **clients = NULL; variable
675 clients = erealloc(clients, sizeof(clients[0]) * (num_clients + 1)); in add_new_socket()
676 clients[num_clients] = c; in add_new_socket()
995 fds[n].fd = clients[n]->fd; in process_loop()
997 if (clients[n]->flags & WAITING_READ) in process_loop()
999 if (clients[n]->flags & WAITING_WRITE) in process_loop()
1012 if (clients[n] == NULL) in process_loop()
1015 clients[n]->flags |= WAITING_CLOSE; in process_loop()
1020 handle_read(clients[n]); in process_loop()
1022 handle_write(clients[n]); in process_loop()
[all …]
/netbsd/src/external/bsd/openldap/dist/doc/rfc/
Drfc3673.txt32 which clients may use to request the return of all operational
37 X.500 [X.500] provides a mechanism for clients to request all
39 to a search operation. This mechanism is often used by clients to
43 (LDAP) [RFC3377] to provide a simple mechanism which clients may use
45 is designed for use with existing general purpose LDAP clients
83 operational attributes using existing LDAP clients. In particular,
85 purpose LDAP clients including those supporting LDAP URLs [RFC2255].
100 This document provides a general mechanism which clients may use to
Drfc2589.txt52 directory services, clients that store dynamic information in the
67 allows a server to inform clients how often they should refresh their
73 directory in a standard LDAP manner, to allow clients to access
76 By definition, dynamic entries are not persistent and clients may go
79 that is scalable. There also must be a mechanism for clients to
82 There must be a way for clients to find out, in a standard LDAP
85 Finally, to allow clients to broadly use the dynamic extensions, the
127 delete, modify and modifyDN operations. However if clients stop
265 directory, and to prevent clients from abusing the dynamic
374 subtrees of the DIT, clients must check the dynamicSubtrees
[all …]
Drfc3663.txt151 o Use a mechanism native to the directory protocol to refer clients
702 output from command line clients, specifically the "ldapsearch"
711 advanced referral chasing were deemed the domain of clients making
712 direct use of LDAP client libraries. Three of these types of clients
716 clients, and the level of control provided by their programming
718 most of the problems encountered with these clients were based on
739 Both the C and Java based clients were built to be both graphical and
742 chosen for both clients proved to be quite capable and offered the
745 construction of both clients, based on past experience, were that the
751 time to create. Both clients are available under the terms of an
[all …]
Drfc3928.txt147 The LCUP protocol is intended to allow LDAP clients to synchronize
152 - Mobile clients that maintain a local read-only copy of the
189 particular group of clients (e.g., on-line clients or off-line
190 clients), none satisfies the requirements of all clients in the
196 information specific to individual clients. The server may need to
198 deleted entries, and moved/renamed entries. The clients are
203 retrieve the changes. LCUP design requires clients to initiate the
290 to LCUP clients. For cookie schemes that expose their value, the
630 Some clients may have unreliable connections, for example, a wireless
631 device or a WAN connection. These clients may want to insure that
[all …]
/netbsd/src/usr.sbin/tcpdchk/
Dtcpdchk.c334 int clients = 0; in check_client_list() local
350 clients = 0; in check_client_list()
352 clients++; in check_client_list()
361 if (clients == 0) in check_client_list()
/netbsd/src/external/ibm-public/postfix/dist/
DRELEASE_NOTES-3.957 [Feature 20240129] In the mysql: and pgsql: clients, the hard-coded
168 <CR><LF>.<CR><LF>, but allows bare newlines from SMTP clients,
201 # Such clients can be allowlisted with smtpd_forbid_bare_newline_exclusions.
202 # The example below allowlists SMTP clients in trusted networks.
213 # This will reject email from SMTP clients that send any non-standard
222 # Such clients can be allowlisted with smtpd_forbid_bare_newline_exclusions.
223 # The example below allowlists SMTP clients in trusted networks.
238 remote SMTP clients that violate RFC 2920 (or 5321) command pipelining
DRELEASE_NOTES-2.849 will reject clients when the lookup result is 127.0.0.2, 127.0.0.4,
53 rejects the same clients.
318 with an adjustable threshold to block SMTP clients with DNSBL score
365 before clients are allowed to talk to a real Postfix SMTP server.
366 It detects clients that start talking too soon, or clients that
367 appear on DNS blocklists, or clients that hang up without sending
380 any checks on clients in mynetworks (primarily, to avoid problems
DRELEASE_NOTES-3.159 that may authenticate clients with a TLS certificate, without having
129 policy service endpoint among multiple check_policy_service clients.
179 updated from 1024 to 2048 bits, because SMTP clients are starting
184 clients. See FORWARD_SECRECY_README for some hints in the quick-start
/netbsd/src/games/hunt/
DREADME.protocol11 The game of hunt is played with one server and several clients. The clients
12 act as dumb 'graphics' clients in that they mostly only ever relay the
43 respond appropriately. This is because clients will not be able to
48 clients can extract a particular server's network address from
54 This is useful for clients broadcasting for any available games. eg:
/netbsd/src/usr.sbin/ndbootd/
DREADME11 makes the raw blocks of a disk available to network clients. Contrast
31 ndbootd exports a disk that the clients consider to be /dev/ndp0 (ND
43 boot program available to clients. When --boot2 is used with a
45 to be served to all clients.
/netbsd/src/usr.sbin/bootp/bootpd/
DProblems19 those clients using numeric form.
30 My huge bootptab file causes startup time to be so long that clients
41 My bootp clients are given responses with a boot file name that is
DAnnounce19 extension files for all clients using bootpef.
35 (this annoyed some clients...)
/netbsd/src/external/bsd/wpa/dist/src/radius/
Dradius_server.c140 struct radius_client *clients; member
335 struct radius_client *client = data->clients; in radius_server_get_client()
2017 struct radius_client *clients) in radius_server_free_clients() argument
2021 client = clients; in radius_server_free_clients()
2041 struct radius_client *clients, *tail, *entry; in radius_server_read_clients() local
2061 clients = tail = NULL; in radius_server_read_clients()
2169 clients = tail = entry; in radius_server_read_clients()
2178 radius_server_free_clients(NULL, clients); in radius_server_read_clients()
2179 clients = NULL; in radius_server_read_clients()
2185 return clients; in radius_server_read_clients()
[all …]
/netbsd/src/external/bsd/iscsi/dist/doc/
DHOWTO-iSCSI-target.txt15 The iSCSI target serves up block storage to clients on the network.
16 These clients are called "initiators". Firstly, we must decide how
/netbsd/src/external/bsd/openldap/dist/doc/drafts/
Ddraft-wahl-ldap-session-xx.txt67 version 3 (LDAP) clients can include session tracking identifiers
69 controls in the requests the clients send to LDAP servers. The LDAP
75 returned to clients and other servers. Three formats of session
129 known as Directory User Agents, which were the clients of the
131 deployments, a majority of LDAP clients were desktop applications,
135 Today, the majority of LDAP clients are embedded within middleware
150 a directory server that has been accessed only by clients that are
419 clients in requests it generates, without modification. A service
424 clients. (If there are multiple proxies involved, each will add
518 be used in LDAP clients that are part of or used by RADIUS servers
[all …]
/netbsd/src/share/examples/fstab/
Dfstab.nfs.23 # Sample fstab file for diskless clients using NFS.

12345678910>>...12