summaryrefslogtreecommitdiffstats
path: root/compat/imsg.c
AgeCommit message (Collapse)Author
2024-01-17Update imsg.Nicholas Marriott
2018-04-23Sync imsg from OpenBSD.Nicholas Marriott
2017-04-11Update imsg*.c from OpenBSD.Nicholas Marriott
2017-03-24Update imsg*.[ch] from OpenBSD, add some compat bits it needs and remove someNicholas Marriott
bits it doesn't.
2017-01-25compat/* should not include tmux.h.Nicholas Marriott
2015-10-15Fix available_fds when there is no AF_INET, reported by Mathieu Arnold.Nicholas Marriott
2015-07-12Update imsg*.[ch] from OpenBSD, including bzero->memset.Nicholas Marriott
2015-05-07queue.h should come from compat.h.Nicholas Marriott
2014-11-08No need for $Id$ now.Nicholas Marriott
2014-08-09Sync libutil from OpenBSD (imsg)Thomas Adam
Changes in the imsg API need to be reflected here as tmux wasn't creating any clients because of it.
2013-06-25+strings.h in compat/.Nicholas Marriott
2011-07-09Expand the Id keyword. Tiago Cunha
2010-11-13Whoops, get the logic the right way round.Nicholas Marriott
2010-11-11malloc(0) may return NULL, so only assume that is an error if allocatingNicholas Marriott
more than zero.
2010-06-06Sync OpenBSD patchset 706:Tiago Cunha
Rename some imsg bits to make namespace collisions less likely buf to ibuf, buf_read to ibuf_read, READ_BUF_SIZE to IBUF_READ_SIZE.
2010-04-12Sync OpenBSD patchset 680:Tiago Cunha
Remove XXX comment and just close received fd if calloc() fails. If this happens the imsg may no longer be usable as there may be queued messages, but this is a) already the case with the code now, and b) would be the case if recvmsg() fails anyway, so we can document that -1 from imsg_read() invalidates the struct imsgbuf. discussed with and ok eric
2009-08-20Add $Id$, nuke queue.h.Nicholas Marriott
2009-08-14Adjust imsg changes to the portable version due to OpenBSD patchset 243.Tiago Cunha
2009-08-14Sync OpenBSD patchset 243:Tiago Cunha
Switch tmux to use imsg. This is the last major change to make the client-server protocol more resilient and make the protocol versioning work properly. In future, the only things requiring a protocol version bump will be changes in the message structs, and (when both client and server have this change) mixing different versions should nicely report an error message. As a side effect this also makes the code tidier, fixes a problem with the way errors reported during server startup were handled, and supports fd passing (which will be used in future). Looked over by eric@, thanks. Please note that mixing a client with this change with an older server or vice versa may cause tmux to crash or hang - tmux should be completely exited before upgrading.