mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Problem : can't make pipe non-blocking on 2.5.X
Date: Wed, 14 Aug 2002 11:19:03 -0700	[thread overview]
Message-ID: <20020814181902.GA24047@bougret.hpl.hp.com> (raw)

	Hi,

	I've got the following problem : I can't make a pipe
non-blocking with 2.5.25.
	The various man pages don't mention anything
about it (actually, the "fifo" man page say that non-blocking mode
should succeed). And it seems to work fine on 2.4.20.
	Sorry if this has already been reported and fixed, but I
quicly searched the changelog and archive and found nothing.

	So, who should I complain to ?

------------- Setup ------------------------
	Kernel : 2.5.25 fails (but 2.4.20-pre2 works)
	Distrib : Debian 3.0
	libc : 2.2.5
------------- Test program -----------------
#include <unistd.h>
#include <fcntl.h>
#include <errno.h>
#include <stdio.h>

int main()
{
  int trigger_pipe[2];
  int err;
  int flags;

  pipe(trigger_pipe);

  err = fcntl(trigger_pipe[0], F_GETFL, &flags);
  fprintf(stderr, "GET FLAGS : %d - %X\n", err, flags);
  if(err >= 0)
    {
      flags |= O_NONBLOCK;
      err = fcntl(trigger_pipe[0], F_SETFL, flags);
      fprintf(stderr, "SET FLAGS : %d - %d\n", err, errno);
    }
  return(0);
}
------------- Output 2.5.25 ----------------
GET FLAGS : 0 - 40045F18
SET FLAGS : -1 - 22
------------- Output 2.4.20-pre2 -----------
GET FLAGS : 0 - 40043F18
SET FLAGS : 0 - 0
--------------------------------------------

	Have fun...

	Jean

             reply	other threads:[~2002-08-14 18:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14 18:19 Jean Tourrilhes [this message]
2002-08-14 18:43 ` Richard B. Johnson
2002-08-14 18:54   ` Jean Tourrilhes
2002-08-14 21:46 ` OGAWA Hirofumi
2002-08-14 21:52   ` Jean Tourrilhes

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=20020814181902.GA24047@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=jt@hpl.hp.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®