domain sockets not cleaning up after themselves

[dshaw]

This one's pleasantly easy to reproduce:

var net = require('net');
var path = '/tmp/echo.sock';
var server = net.createServer(function(c) {
    console.log('server connected');
      c.on('end', function() {
            console.log('server disconnected');
              });
        c.write('hello\r\n');
          c.pipe(c);
});
server.listen(path, function() {
    console.log('server bound on %s', path);
});

Running this more than once will throw Error: listen EADDRINUSE. The file system artifact is not getting cleaned up.

[dshaw]

My original gist: https://gist.github.com/9f93cdcd3a77b9142e51

[bnoordhuis]

That's by design. Older versions of node used to unlink the socket but that was subject to heinous race conditions in multi-process setups.

I realize that's never been documented on the API changes page. Well, it is now. :-)

[piscisaureus]

@bnoordhuis Does the socket file get removed when you close() the server, or when node gracefully exits?

[bnoordhuis]

@piscisaureus server.close() unlinks the socket (which perhaps isn't a great idea, either), process.exit() or throw 42 won't.

[piscisaureus]

@bnoordhuis Yeah, that will break in a cluster scenario.

[aslilac]

@bnoordhuis Could a note of this behavior be added to the regular documentation as well?

[dayuoba]

I got the same problem,i do not know why that was by design that node won't unlink path when exit in any case.