On Tue, 8 Jan 2019 at 20:02, Ben Noordhuis <[email protected]> wrote: > There's no absolute guarantee because libuv just bubbles up the error > from the operating system. Most of the time you'll see UV_EADDRINUSE > but, for example, macos might return UV_EACCES if the address is > protected. (I'm 90% sure the kernel's protection check comes before > the already-in-use check.) > > I wouldn't expect to see UV_EADDRNOTAVAIL, that's the error code for > when you're trying to bind to an address that isn't owned by the local > machine.
That's exactly what I meant: whether UV_EADDRNOTAVAIL is just for attempts to bind an address that isn't owned by the machine. If guaranteed I'm done. :) Thanks. -- Iñaki Baz Castillo <[email protected]> -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
