[+tmux-users]
On 2014-06-03 09:06 +0200, Michael Wild wrote:
> Also, refer to https://cygwin.com/ml/cygwin/2014-06/msg00008.html.
> Perhaps this helps you tracking down what exactly triggers this
> behaviour.
That post has the following fragment:
> > Here's the strace I got:
> > cygwin-1.7.30-1:
> > 96 1063224 [main] tmux 4072 cygwin_connect: -1 = connect(5,
> > 0x229780, 24), errno 0
> > cygwin-1.7.29-2:
> > 92 1054064 [main] tmux 3548 cygwin_connect: -1 = connect(5,
> > 0x229780, 24), errno 111
So this means errno handling has changed in cygwin. Btw, errno 111 means
ECONNREFUSED. In tmux's client_connect() in client.c you have this
fragment:
...
if (connect(fd, (struct sockaddr *) &sa, SUN_LEN(&sa)) == -1) {
if (errno != ECONNREFUSED && errno != ENOENT)
goto failed;
...
This does mean tmux does things differently based on the errno value. I
don't have much time right now to play around with this but maybe you
could look into cygwin in the meantime?
--
Balazs
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
