node package manager

Introducing npm Enterprise add-ons. Integrate third-party dev tools into npm…


Unix datagram socket


Communicate over UNIX datagram sockets.


// One-shot server.  Note that the server cannot send a reply;
// UNIX datagram sockets are unconnected and the client is not addressable.
var unix = require('unix-dgram');
var server = unix.createSocket('unix_dgram', function(buf) {
  console.log('received ' + buf);


// Send a single message to the server.
var message = Buffer('ping');
var client = unix.createSocket('unix_dgram');
client.on('error', console.error);
client.send(message, 0, message.length, '/path/to/socket');

Caveat emptor: events and callbacks are synchronous for efficiency reasons.

Returns a new unix.Socket object. type should be 'unix_dgram'. Throws an exception if the socket(2) system call fails.

The optional listener argument is added as a listener for the 'message' event. The event listener receives the message as a Buffer object as its first argument.

Create a server at path. Emits a 'listening' event on success or an 'error' event if the bind(2) system call fails.

Associate a socket with a remote path so you can send a message without setting the remote path. Once the socket is connected it emits a 'connect' event. It also allows to perform some kind of congestion control as it emits a 'congestion' event when the receiving buffer is full, and a 'writable' event when it stops being full.

Only to be used with connected sockets. It sends a message to the remote path associated with the socket


var unix = require('unix-dgram');

var client = unix.createSocket('unix_dgram');

client.on('error', function(err) {

client.on('connect', function() {
    client.on('congestion', function() {
        /* The server is not accepting data */

    client.on('writable', function() {
        /* The server can accept data */

    var message = new Buffer('PING');


Send a message to the server listening at path.

buf is a Buffer object containing the message to send, offset is the offset into the buffer and length is the length of the message.

For backwards compatibility, you can still use the socket.send function with this same signature.


var buf = new Buffer('foobarbaz');
socket.send(buf, 3, 4, '/path/to/socket');  // Sends 'barb'.

Close the socket. If the socket was bound to a path with socket.bind(), then you will no longer receive new messages. The file system entity (the socket file) is not automatically unlinked.