Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • Do named pipes do what you want? If not, edit to explain why. Commented Nov 22, 2017 at 19:43
  • Hmm... as far as I'm aware named pipes only have one consumer, or at least the lines are only received by the earliest connected pipe. Commented Nov 22, 2017 at 19:46
  • Hmm, the O_ASYNC flag to open might cause data to be sent to all connected processes. Commented Nov 22, 2017 at 19:58
  • I don't think this async mode is particularly related. It just seems like a way to "wake up a process" when it should be reading or writing. Commented Nov 22, 2017 at 20:17
  • 1
    Maybe. I would note that language as a rule tends to be ambiguous because the world is quite big :P. I think most people would view using a pipe as quite different in nature from, say, a RabbitMQ server. I guess what I really mean is "without having to setup, manage, configure and monitor a process." I'll update the question to this effect. Things like dbus are an interesting middleg-round: always running and (I think?) configuration-free. This does make me depend on X... I think. Commented Nov 22, 2017 at 22:50