diff options
author | Brian Ashworth <bosrsf04@gmail.com> | 2019-04-17 01:57:34 -0400 |
---|---|---|
committer | Simon Ser <contact@emersion.fr> | 2019-04-17 09:07:08 +0300 |
commit | d7d29fe546ab0acb332013eb380f8193e1d5b9fc (patch) | |
tree | 06bf13f5f682906ee3d705aa9287cc29c5b8b7f1 /common | |
parent | aa4deef8a86ccddbd0d9a7d894e72ac329d8960d (diff) |
swaymsg: add timeout and type checks
This adds a 3 second timeout to the initial reply in swaymsg. This
prevents swaymsg from hanging when `swaymsg -t get_{inputs,seats}` is
used in i3. The timeout is removed when waiting for a subscribed event
or monitoring for subscribed events.
This also adds type checks to commands where i3 does not reply with all
of the properties that sway does (such as `modes` in `get_outputs`).
This is mostly just a behavioral adjustment since swaymsg should run on
i3. When running under i3, some command reply's (such as the one for
`get_outputs) may have more useful information in the raw json than the
pretty printed version.
Diffstat (limited to 'common')
-rw-r--r-- | common/ipc-client.c | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/common/ipc-client.c b/common/ipc-client.c index 13e2dfa3..b6c03d13 100644 --- a/common/ipc-client.c +++ b/common/ipc-client.c @@ -69,6 +69,16 @@ int ipc_open_socket(const char *socket_path) { return socketfd; } +bool ipc_set_recv_timeout(int socketfd, struct timeval tv) { + if (setsockopt(socketfd, SOL_SOCKET, SO_RCVTIMEO, &tv, sizeof(tv)) == -1) { + sway_log_errno(SWAY_ERROR, "Failed to set ipc recv timeout"); + return false; + } + sway_log(SWAY_DEBUG, "ipc recv timeout set to %ld.%06ld", + tv.tv_sec, tv.tv_usec); + return true; +} + struct ipc_response *ipc_recv_response(int socketfd) { char data[IPC_HEADER_SIZE]; uint32_t *data32 = (uint32_t *)(data + sizeof(ipc_magic)); |