linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sumit Narayan" <sumit_uconn@lycos.com>
To: fdavis@si.rr.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Write file in EXT2
Date: Tue, 06 May 2003 10:52:27 -0400	[thread overview]
Message-ID: <JLODCPDJJDNBCDAA@mailcity.com> (raw)

Hi,

Thanks for the details.

I wish to know which application access which file, when.. etc etc. I would like to create a log of that. I am unable to write this log to the file from within the kernel. I would not like to go to the user level programs. I am doing this from within the kernel, as I would like to know exactly when things are being done.

Regards,
Sumit
--

On Tue, 06 May 2003 01:06:45  
 Frank Davis wrote:
>Sumit,
>
>In fact, if you're looking at journalizing ext2, ext3 has already done it.
>
>Regards,
>Frank
>
>Frank Davis wrote:
>> Sumit,
>> 
>> Why do you have to do this in the kernel? I can envision doing printks 
>> after each read and write call, and having a userland program receive 
>> the kernel output, storing it into a buffer, and then writing that 
>> buffer, either using fprintf, or fflush, etc.
>> 
>> Regards,
>> Frank
>> 
>> Sumit Narayan wrote:
>> 
>>> Hi,
>>>
>>> I would like to create a log file containing the reads and writes made 
>>> on a disk, by adding a function in the kernel. And once this log table 
>>> reaches a limit, say 10,000 records, I would like it to be written on 
>>> hard disk automatically. I am unable to do this, since I dont know how 
>>> to write to a file, while in the kernel. I tried System Calls, but 
>>> they dont seem to work. Could someone tell me what is the list of 
>>> functions that I need to use to do this job. I think I have to play 
>>> with super-blocks and inodes. But I dont know how to do that. :) 
>>> Please help me.
>>> Thanks.
>>> Sumit
>>>
>>> p.s. I am using Kernel 2.4.20 and want this in EXT2 FS
>>>
>>>
>>> ____________________________________________________________
>>> Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
>>> http://login.mail.lycos.com/r/referral?aid=27005
>>> -
>>> To unsubscribe from this list: send the line "unsubscribe 
>>> linux-kernel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>> Please read the FAQ at  http://www.tux.org/lkml/
>>>
>> 
>> 
>
>
>


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

             reply	other threads:[~2003-05-06 14:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 14:52 Sumit Narayan [this message]
2003-05-07 16:55 ` Write file in EXT2 Amol P Dharmadhikari
  -- strict thread matches above, loose matches on Subject: below --
2003-05-06 14:45 Sumit Narayan
2003-05-06 15:34 ` Richard B. Johnson
2003-05-06  3:14 Sumit Narayan
2003-05-06  4:10 ` Valdis.Kletnieks
2003-05-06  7:17 ` Matti Aarnio

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=JLODCPDJJDNBCDAA@mailcity.com \
    --to=sumit_uconn@lycos.com \
    --cc=fdavis@si.rr.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;
as well as URLs for NNTP newsgroup(s).