13 releases

0.7.1 Nov 15, 2023
0.7.0 Mar 3, 2023
0.6.0 Mar 3, 2023
0.5.6 Nov 30, 2022
0.3.0 Nov 6, 2020

#71 in Unix APIs

Download history 5475/week @ 2024-01-03 6378/week @ 2024-01-10 5001/week @ 2024-01-17 5904/week @ 2024-01-24 7446/week @ 2024-01-31 6569/week @ 2024-02-07 7609/week @ 2024-02-14 6413/week @ 2024-02-21 6290/week @ 2024-02-28 6219/week @ 2024-03-06 7216/week @ 2024-03-13 7135/week @ 2024-03-20 7877/week @ 2024-03-27 7508/week @ 2024-04-03 6913/week @ 2024-04-10 5673/week @ 2024-04-17

29,458 downloads per month
Used in 2 crates



Docs.rs Tests


Unix seqpacket sockets for tokio.

Seqpacket sockets combine a number of useful properties:

  • They are connection oriented.
  • They guarantee in-order message delivery.
  • They provide datagrams with well-defined semantics for passing along file descriptors.

These properties make seqpacket sockets very well suited for local servers that need to pass file-descriptors around with their clients.

You can create a UnixSeqpacketListener to start accepting connections, or create a UnixSeqpacket to connect to a listening socket. You can also create a pair of connected sockets with UnixSeqpacket::pair().

Passing file descriptors and other ancillary data.

You can use send_vectored_with_ancillary and recv_vectored_with_ancillary to send and receive ancillary data. This can be used to pass file descriptors and unix credentials over sockets.

&self versus &mut self

Seqpacket sockets have well-defined semantics when sending or receiving on the same socket from different threads. Although the order is not guaranteed in that scenario, each datagram will be delivered intact. Since tokio 0.3, it is also possible for multiple tasks to await the same file descriptor. As such, all I/O functions now take &self instead of &mut self, and the split() API has been deprecated.


use tokio_seqpacket::UnixSeqpacket;

let mut socket = UnixSeqpacket::connect("/run/foo.sock").await?;

let mut buffer = [0u8; 128];
let len = socket.recv(&mut buffer).await?;
println!("{}", String::from_utf8_lossy(&buffer[..len]));


~106K SLoC