public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Arijit Das <Arijit.Das@synopsys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does Linux has File Stream mapping support...?
Date: Fri, 18 Nov 2005 20:14:15 +0000	[thread overview]
Message-ID: <437E3617.8000207@superbug.demon.co.uk> (raw)
In-Reply-To: <7EC22963812B4F40AE780CF2F140AFE920904A@IN01WEMBX1.internal.synopsys.com>

Arijit Das wrote:
> Is it possible to have File Stream Mapping in Linux? What I mean is
> this...
> 
> FILE * fp1 = fopen("/foo", "w");
> FILE * fp2 = fopen("/bar", "w");
> FILE * fp_common = <Stream_Mapping_Func>(fp1, fp2);
> 
> fprint(fp_common, "This should be written to both files ... /foo and
> /bar");
> 
> So, what I am looking for is anything written to "fp_common" should
> actually be written to the streams fp1 and fp2.
> 
> Does Linux support this any way? Is there any way to achieve this...? Is
> there anything like <Stream_Mapping_Func>(above) ...?
> 
> Do pardon me if you feel that it is a wrong Forum to ask this question
> but I tried everywhere else and thought that implementers would best
> know about it, if at all anything like that exists.
> 
> Thanks,
> Arijit
> -

Why not just output to a file, and then use "tail -f filename"


  reply	other threads:[~2005-11-18 20:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18 10:38 Does Linux has File Stream mapping support...? Arijit Das
2005-11-18 20:14 ` James Courtier-Dutton [this message]
2005-11-18 20:41   ` linux-os (Dick Johnson)
2005-11-19  4:27 ` Herbert Xu
     [not found] <5abPs-7Da-41@gated-at.bofh.it>
2005-11-18 12:30 ` Bodo Eggert
  -- strict thread matches above, loose matches on Subject: below --
2005-11-18 12:51 Arijit Das
2005-11-18 12:59 ` Bas Westerbaan
2005-11-18 13:01   ` Bas Westerbaan
2005-11-18 14:28     ` Dick Streefland
2005-11-18 19:06 ` Bill Davidsen
2005-11-18 19:39 ` Lennart Sorensen
2005-11-21  9:18 ` Jim Nance

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=437E3617.8000207@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=Arijit.Das@synopsys.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