From: jlb@visi.com (Joel L. Breazeale)
To: linux-kernel@vger.kernel.org
Subject: May be off topic: ioctl I_SETSIG S_INPUT setting not valid for a named pipe?
Date: Sat, 19 Apr 2003 23:13:33 -0500 (CDT) [thread overview]
Message-ID: <20030420041333.56A8376CA2@isis.visi.com> (raw)
I have a set of programs which practically demonstrate the I_SETSIG ioctl
command does not work with the S_INPUT constant for a named pipe. The errno
value returned by the ioctl call is 22. Two kernel versions demonstrating
this problem are 2.4.18-3 and 2.4.20-9.
I have already sent the details of this problem, including the sample
programs, in a message on 14 Apr 2003 with a subject of "PROBLEM: ioctl()
I_SETSIG S_INPUT option fails on a FIFO" to this mailing list. I would be
glad to send to anyone upon request.
Here are my questions:
* Is the above ioctl deprecated for named pipes?
* Who is the maintainer of this functionality (who presonally is
willing to receive a problem report on this matter)?
[I would greatly appreciate a personal e-mail on this subject as I may be
dropping from this mailing list shortly due to volume and apparently lack
of interest in this subject.]
Thank you,
Joel Breazeale
reply other threads:[~2003-04-20 4:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030420041333.56A8376CA2@isis.visi.com \
--to=jlb@visi.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®