Searched refs:connecting (Results 1 – 7 of 7) sorted by relevance
87 … bool connecting; /* This boolean indicates whether the socket fd we are operating on is currently member299 … v->connecting = true; /* We are asynchronously connecting, i.e. the connect() is being in varlink_connect_address()398 if (v->connecting) in varlink_test_disconnect()439 …if (v->connecting) /* Writing while we are still wait for a non-blocking connect() to complete will in varlink_write()494 …if (v->connecting) /* read() on a socket while we are in connect() will fail with EINVAL, hence ex… in varlink_read()1011 if (v->connecting) { in handle_revents()1019 v->connecting = false; in handle_revents()1095 … if (v->connecting) /* When processing an asynchronous connect(), we only wait for EPOLLOUT, which in varlink_get_events()
156 this case should be pretty obvious: try connecting a socket to
182 implemented by systemd. Transparently for your client code connecting to the
264 When connecting to untrusted WiFi networks it might be wise to go one step
271 connecting the host system to the container/VM spawned by mkosi. Once systemd-networkd is running, …
127 * maybe add support for binding and connecting AF_UNIX sockets in the file128 system outside of the 108ch limit. When connecting, open O_PATH fd to socket668 * sd-bus: when connecting to some dbus server socker, set originating AF_UNIX1356 - port to sd-resolve for connecting to TCP dbus servers
2061 acquired by connecting to that socket and reading from it. This5382 new "append:…" parameters, for connecting STDOUT/STDERR of a service8289 running. This allows easy connecting of multiple containers with a10767 * systemctl's -H switch for connecting to remote systemd10874 connecting to these facilities even if PrivateDevices=yes is11571 * A proxy daemon is now provided to proxy clients connecting