From: Dan Gary <funkychunkymunky@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: File I/O wrapper?
Date: Mon, 24 Jan 2005 11:55:14 -0800 [thread overview]
Message-ID: <1450f66c05012411557e328fa1@mail.gmail.com> (raw)
I'm working on a new logging system and came across the idea of using
a program through a symbolic link instead of a file for a log.
Basically I would write a program that logs to a variety of
configurable sources, and would act as a file when it comes to I/O,
doing whatever processing I want in between the "actual" file and the
calling program.
My only hang up so far is actually getting the program to emulate file
I/O without writing to the program file itself.
So in simple terms, I want a program to act like a file, and I'm stuck on How.
A FIFO isn't quite what I need, but close, although I need a single
point of reference to handle all I/O, exactly like a file.
And I can't/don't want to rewrite every potential calling program to
work with this.
I've been thinking I'm going to have to do a kernel module, but I was
hoping someone might know a way I can implement this w/o doing a kmod.
I've always been a higher level programmer, interfaces, DB
access/filtering, etc, so anything as low as throwing a hook into file
I/O is a little beyond my existing knowledge level, but I'm willing to
give it a shot.
Any help would be greatly appreciated.
next reply other threads:[~2005-01-24 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 19:55 Dan Gary [this message]
2005-01-25 5:49 ` File I/O wrapper? Rafael
[not found] ` <200501241454.21502.eric@cisu.net>
[not found] ` <1450f66c05012508457a3f123c@mail.gmail.com>
2005-01-25 19:42 ` Eric Bambach
2005-01-30 11:45 ` Glynn Clements
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=1450f66c05012411557e328fa1@mail.gmail.com \
--to=funkychunkymunky@gmail.com \
--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).