Re: [patch] netcat: don't call report_connect() when family == AF_UNIX

Bob Beck writes: >> Hi tech@, >> >> I just ran into this while fiddling with some netcat-based plumbing. >> When I connect to the specified socket from another shell, the >> listening nc dies if it is AF_UNIX: >> >> $ tail -10f /var/log/messages | nc -vkU -l ~/.xlog_socket >> nc: getna

Re: [patch] netcat: don't call report_connect() when family == AF_UNIX

if you write regress ill happily take them try to make a few for regular and tls connections and failures On Saturday, 28 May 2016, attila wrote: > > Bob Beck > writes: > > >> Hi tech@, > >> > >> I just ran into this while fiddling with some netcat-based plumbing. > >> When I connect to the spe

Re: [patch] netcat: don't call report_connect() when family == AF_UNIX

Bob Beck writes: >> Hi tech@, >> >> I just ran into this while fiddling with some netcat-based plumbing. >> When I connect to the specified socket from another shell, the >> listening nc dies if it is AF_UNIX: >> >> $ tail -10f /var/log/messages | nc -vkU -l ~/.xlog_socket >> nc: getna

Re: [patch] netcat: don't call report_connect() when family == AF_UNIX

> Hi tech@, > > I just ran into this while fiddling with some netcat-based plumbing. > When I connect to the specified socket from another shell, the > listening nc dies if it is AF_UNIX: > > $ tail -10f /var/log/messages | nc -vkU -l ~/.xlog_socket > nc: getnameinfo: Invalid argument >

[patch] netcat: don't call report_connect() when family == AF_UNIX

Hi tech@, I just ran into this while fiddling with some netcat-based plumbing. When I connect to the specified socket from another shell, the listening nc dies if it is AF_UNIX: $ tail -10f /var/log/messages | nc -vkU -l ~/.xlog_socket nc: getnameinfo: Invalid argument The attached patch