From: Michael Vines <mjvines@undergrad.math.uwaterloo.ca>
To: Catalin BOIE <util@deuroconsult.ro>
Cc: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>, linux-kernel@vger.kernel.org
Subject: Re: Kernel hook for open
Date: Mon, 6 Nov 2000 10:11:11 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.10.10011061009490.9936-100000@barkingdogstudios.com> (raw)
In-Reply-To: <20001106155702.F12348@arthur.ubicom.tudelft.nl>
On Mon, 6 Nov 2000, Erik Mouw wrote:
> On Mon, Nov 06, 2000 at 03:55:41PM +0200, Catalin BOIE wrote:
> > I wish to know if there is something like a kernel hook for open function.
> > I want to monitor a file (someting like watchdog on Solaris) and to read
> > from my own process (module?) and from the file.
>
> I don't know what watchdog is, but maybe strace is what you want (man
> strace for more info).
>
> > I tried with LD_SO_PRELOAD but it haven't any effect on the so libraries.
> > For example:
> > If I use function getpwent (that is in a so library) and my home
> > made .so library that overwrite "open" function and is in
> > /etc/ld.so.preload file it doesn't work.
> > Of course, if I use open ("/etc/hosts") the so library execute my
> > function.
>
> Use LD_PRELOAD instead.
You could also write a simple kernel module that replaces the open system
call. See the Linux Kernel Module Programming Guide for details.
http://www.linuxdoc.org/guides.html
specifically http://www.linuxdoc.org/LDP/lkmpg/node20.html
Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-06 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 13:55 Catalin BOIE
2000-11-06 14:57 ` Erik Mouw
2000-11-06 15:11 ` Michael Vines [this message]
2000-11-06 17:20 ` Erik Mouw
2000-11-06 17:40 ` Michael Vines
2000-11-07 10:58 ` Catalin BOIE
2000-11-07 10:53 ` Catalin BOIE
2000-11-07 11:06 ` Tigran Aivazian
2000-11-07 11:09 ` Tigran Aivazian
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=Pine.LNX.4.10.10011061009490.9936-100000@barkingdogstudios.com \
--to=mjvines@undergrad.math.uwaterloo.ca \
--cc=J.A.K.Mouw@ITS.TUDelft.NL \
--cc=linux-kernel@vger.kernel.org \
--cc=util@deuroconsult.ro \
/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®