From: Henry Margies <henry.margies@gmx.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: Problem with read() and named pipe (FIFO)
Date: Mon, 16 Aug 2004 16:57:45 +0200 [thread overview]
Message-ID: <20040816165745.3ccf3356.henry.margies@gmx.de> (raw)
In-Reply-To: <20040816144752.43149.qmail@web12701.mail.yahoo.com>
Hi
Have you tried fflush or fsync or something like this?
Henry
--
Hi! I'm a .signature virus! Copy me into your
~/.signature to help me spread!
next prev parent reply other threads:[~2004-08-16 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 14:47 Problem with read() and named pipe (FIFO) Hossein Mobahi
2004-08-16 14:57 ` Henry Margies [this message]
2004-08-17 10:58 ` Problem with read() and named pipe (FIFO) (fflush or fsync) Hossein Mobahi
2004-08-17 3:21 ` Problem with read() and named pipe (FIFO) joy
2004-08-17 10:55 ` Problem with read() and named pipe (FIFO) (pipe not disk) Hossein Mobahi
2004-08-17 17:58 ` joy
2004-08-17 19:24 ` Hossein Mobahi
2004-08-17 19:25 ` Hossein Mobahi
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=20040816165745.3ccf3356.henry.margies@gmx.de \
--to=henry.margies@gmx.de \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).