| Port details |
- p5-Atomic-Pipe Send atomic messages from multiple writers across a POSIX pipe
- 0.023 devel
=0 Package not present on quarterly.This port was created during this quarter. It will be in the next quarterly branch but not the current one. - Maintainer: sunpoet@FreeBSD.org
 - Port Added: 2026-04-18 22:03:23
- Last Update: 2026-04-18 21:18:13
- Commit Hash: 7f4a795
- Also Listed In: perl5
- License: ART10 GPLv1+
- WWW:
- https://metacpan.org/dist/Atomic-Pipe
- Description:
- Normally if you write to a pipe from multiple processes/threads, the messages
will come mixed together unpredictably. Some messages may be interrupted by
parts of messages from other writers. This module takes advantage of some POSIX
specifications to allow multiple writers to send arbitrary data down a pipe in
atomic chunks to avoid the issue.
NOTE: This only works for POSIX compliant pipes on POSIX compliant systems. Also
some features may not be available on older systems, or some platforms.
Under the hood this module will split your message into small sections of
slightly smaller than the PIPE_BUF limit. Each message will be sent as 1 atomic
chunk with a 4 byte prefix indicating what process id it came from, what thread
id it came from, a chunk ID (in descending order, so if there are 3 chunks the
first will have id 2, the second 1, and the final chunk is always 0 allowing a
flush as it knows it is done) and then 1 byte with the length of the data
section to follow.
On the receiving end this module will read chunks and re-assemble them based on
the header data. So the reader will always get complete messages. Note that
message order is not guarenteed when messages are sent from multiple processes
or threads. Though all messages from any given thread/process should be in
order.
¦ ¦ ¦ ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - USE_RC_SUBR (Service Scripts)
- no SUBR information found for this port
- Dependency lines:
-
- p5-Atomic-Pipe>0:devel/p5-Atomic-Pipe
- To install the port:
- cd /usr/ports/devel/p5-Atomic-Pipe/ && make install clean
- To add the package, run one of these commands:
- pkg install devel/p5-Atomic-Pipe
- pkg install p5-Atomic-Pipe
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: p5-Atomic-Pipe
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1775587090
SHA256 (Atomic-Pipe-0.023.tar.gz) = ca72bccf0ace8032a58b17e58a416d4293f1c3442d5b5a0d893b27b491a8a688
SIZE (Atomic-Pipe-0.023.tar.gz) = 37349
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- perl5>=5.42.r<5.43 : lang/perl5.42
- Runtime dependencies:
-
- perl5>=5.42.r<5.43 : lang/perl5.42
- There are no ports dependent upon this port
Configuration Options:
- No options to configure
- Options name:
- devel_p5-Atomic-Pipe
- USES:
- perl5
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 1
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
0.023 18 Apr 2026 21:18:13
    |
Po-Chuan Hsieh (sunpoet)  |
devel/p5-Atomic-Pipe: Add p5-Atomic-Pipe 0.023
Normally if you write to a pipe from multiple processes/threads, the messages
will come mixed together unpredictably. Some messages may be interrupted by
parts of messages from other writers. This module takes advantage of some POSIX
specifications to allow multiple writers to send arbitrary data down a pipe in
atomic chunks to avoid the issue.
NOTE: This only works for POSIX compliant pipes on POSIX compliant systems. Also
some features may not be available on older systems, or some platforms.
Under the hood this module will split your message into small sections of
slightly smaller than the PIPE_BUF limit. Each message will be sent as 1 atomic
chunk with a 4 byte prefix indicating what process id it came from, what thread
id it came from, a chunk ID (in descending order, so if there are 3 chunks the
first will have id 2, the second 1, and the final chunk is always 0 allowing a
flush as it knows it is done) and then 1 byte with the length of the data
section to follow.
On the receiving end this module will read chunks and re-assemble them based on
the header data. So the reader will always get complete messages. Note that
message order is not guarenteed when messages are sent from multiple processes
or threads. Though all messages from any given thread/process should be in
order. |
Number of commits found: 1
|