From: Mohammed Khalid Ansari <khalid@ncst.ernet.in>
To: Steven Smith <sos22@cam.ac.uk>
Cc: linux c programming mailing list <linux-c-programming@vger.kernel.org>
Subject: Re: how to read a constantly changing file
Date: Wed, 5 Jun 2002 17:09:55 +0530 (IST) [thread overview]
Message-ID: <Pine.LNX.4.33.0206051702360.1073-100000@soochak.ncst.ernet.in> (raw)
In-Reply-To: <20020604095456.GA1012@cam.ac.uk>
That's ok but it is not feasible to open a file every time it changes, go
to the last bytes which appended to the file and print it (tail command)
especially when the filesize is bigger (eg log file). There must be some
other method.
--
**************************************************************************
Mohammed Khalid Ansari Tel (res) : 0091-022-3051360
Assistant Manager II (off) : 0091-022-2024641
National Centre for Software Technology Fax : 0091-022-2049573
8th flr,Air India Build. Nariman Point, E-Mail : khalid@ncst.ernet.in
Mumbai 400021.
Homepage : http://soochak.ncst.ernet.in/~khalid
**************************************************************************
On Tue, 4 Jun 2002, Steven Smith wrote:
> > I want to know how can I read a file (through a C code) which is
> > constatnly changing, like a log file.(eg tail command)
> As far as I can make out, tail does it by sitting in a loop
> and calling sleep(1), and then fstat() to see if the file's grown.
>
> You might be better off looking at directory change notifications
> for the parent directory. The closest thing this has to documentation
> is fs/dnotify.c in the kernel source, though.
>
> Steven Smith,
> sos22@cam.ac.uk.
>
next prev parent reply other threads:[~2002-06-05 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 9:36 how to read a constantly changing file Mohammed Khalid Ansari
2002-06-04 9:54 ` Steven Smith
2002-06-05 11:39 ` Mohammed Khalid Ansari [this message]
2002-06-05 16:12 ` 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=Pine.LNX.4.33.0206051702360.1073-100000@soochak.ncst.ernet.in \
--to=khalid@ncst.ernet.in \
--cc=linux-c-programming@vger.kernel.org \
--cc=sos22@cam.ac.uk \
/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).