supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Joshua Ismael Haase Hernández" <hahj87@gmail.com>
To: supervision@list.skarnet.org
Subject: How can I make the stdin of a longrun process available to other processes by writing to a file?
Date: Fri, 20 Nov 2020 17:28:53 -0600	[thread overview]
Message-ID: <CA+ypG2ZaXn738E39RRWpQUewiBLE+nkF29iMQLMLs7AYh5A9YQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 538 bytes --]

I hope this message finds you well.

I want to make the stdin of a `skabus-dyntee` process available to others
to communicate.
`skabus-dyntee-client` instances can listen to a service if i make it
available, but I have no way to send messages to them by writing a file.

I've tried:

-  Using a named pipe and have `skabus-dyntee` read from it (and it dies as
soon as the writer program ends).
-  Configuring up s6-fdholder for my user to use (but it seems I don't
understand how to give it the stdin to read).

What would you recommend?

             reply	other threads:[~2020-11-20 23:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 23:28 Joshua Ismael Haase Hernández [this message]
2020-11-20 23:45 ` Laurent Bercot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+ypG2ZaXn738E39RRWpQUewiBLE+nkF29iMQLMLs7AYh5A9YQ@mail.gmail.com \
    --to=hahj87@gmail.com \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).