From: Ihor Antonov <ihor@antonovs.family>
To: supervision@list.skarnet.org
Subject: ftrig pipe naming convention
Date: Sun, 18 Sep 2022 08:41:59 -0700 [thread overview]
Message-ID: <20220918154159.che33klmotj6nps6@localhost> (raw)
Hello
As I was playing with s6 I found out that not every fifo placed in
./event gets notification.
After some digging I found out why.
https://github.com/skarnet/s6/blob/master/src/libs6/ftrigw_notifyb_nosig.c#L33-L34
if (strncmp(d->d_name, FTRIG1_PREFIX ":@", FTRIG1_PREFIXLEN + 2)) continue ;
if (strlen(d->d_name) != FTRIG1_PREFIXLEN + 33) continue ;
I wonder what is the reason behind the naming convention? What is the
downside of simply writing to any present fifo file ?
Thanks
Ihor
next reply other threads:[~2022-09-18 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 15:41 Ihor Antonov [this message]
2022-09-18 20:38 ` Laurent Bercot
2022-09-18 21:11 ` Ihor Antonov
2022-10-04 11:54 ` 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=20220918154159.che33klmotj6nps6@localhost \
--to=ihor@antonovs.family \
--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).