aboutsummaryrefslogtreecommitdiff
path: root/compat/imsg.c
Commit message (Collapse)AuthorAge
* Sync imsg from OpenBSD.Nicholas Marriott2018-04-23
|
* Update imsg*.c from OpenBSD.Nicholas Marriott2017-04-11
|
* Update imsg*.[ch] from OpenBSD, add some compat bits it needs and remove someNicholas Marriott2017-03-24
| | | | bits it doesn't.
* compat/* should not include tmux.h.Nicholas Marriott2017-01-25
|
* Fix available_fds when there is no AF_INET, reported by Mathieu Arnold.Nicholas Marriott2015-10-15
|
* Update imsg*.[ch] from OpenBSD, including bzero->memset.Nicholas Marriott2015-07-12
|
* queue.h should come from compat.h.Nicholas Marriott2015-05-07
|
* No need for $Id$ now.Nicholas Marriott2014-11-08
|
* Sync libutil from OpenBSD (imsg)Thomas Adam2014-08-09
| | | | | Changes in the imsg API need to be reflected here as tmux wasn't creating any clients because of it.
* +strings.h in compat/.Nicholas Marriott2013-06-25
|
* Expand the Id keyword. Tiago Cunha2011-07-09
|
* Whoops, get the logic the right way round.Nicholas Marriott2010-11-13
|
* malloc(0) may return NULL, so only assume that is an error if allocatingNicholas Marriott2010-11-11
| | | | | more than zero.
* Sync OpenBSD patchset 706:Tiago Cunha2010-06-06
| | | | | | 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.
* Sync OpenBSD patchset 680:Tiago Cunha2010-04-12
| | | | | | | | | | | | 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
* Add $Id$, nuke queue.h.Nicholas Marriott2009-08-20
|
* Adjust imsg changes to the portable version due to OpenBSD patchset 243.Tiago Cunha2009-08-14
|
* Sync OpenBSD patchset 243:Tiago Cunha2009-08-14
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.