On 17/03/2015 16:52, Vincent de RIBOU wrote:
Hi all, I assume that read and write separate FDs (6 and 7) are only present as compliancy with other tools which produce 2 real different FDs.But on TCP is not really. I've made TLS client over s6-tcpclient with wolfSSL. This lib takes only 1 FD for context.Since FDs 6 and 7 are same link with s6-tcpclient, I used FD 6 for ctx building and it works. How should I use 2 really different FD's in that context??May I set internal unix concept to mux 2 FD's on 1??
You can simply ignore the second fd, which is just a copy of the first one. You can even close(7) at the start of your client and use 6 everywhere, it will work. -- Laurent
