From: "Orlin Grigorov" <ogrigorov@gmail.com>
To: "Karl Zilles" <zilles@1969web.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] How to monitor a specific file for changes
Date: Mon, 22 Oct 2007 15:57:57 -0400 [thread overview]
Message-ID: <b17e12b30710221257o34db8536w3f98246d46d93b91@mail.gmail.com> (raw)
In-Reply-To: <471CFD24.30805@1969web.com>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
Using "Unix.stat" works perfectly for my purpose! On both platforms,
hurray! THANK YOU!
On 10/22/07, Karl Zilles <zilles@1969web.com> wrote:
>
> Orlin Grigorov wrote:
> > Oh, here's another idea---every certain amount of time, I just compare
> > my last saved version of the file to the current one---if different,
> > there's my event. What do you think?
>
> Just stat it. You can stat it every second and never notice any
> performance issue. In fact you can stat a whole directory of files
> every second and never notice. It'll work cross platform, and it's easy:
>
> let modtime file =
> let filedata = Unix.stat file in
> filedata.Unix.st_mtime
>
>
> In a loop, compare the modtime to the previous modtime, then
> Unix.sleep 1;
>
[-- Attachment #2: Type: text/html, Size: 1239 bytes --]
next prev parent reply other threads:[~2007-10-22 19:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 19:03 Orlin Grigorov
2007-10-22 19:05 ` [Caml-list] " Robert Fischer
2007-10-22 19:09 ` Sylvain Le Gall
2007-10-22 19:11 ` [Caml-list] " Andrew Gacek
2007-10-22 19:20 ` Erik de Castro Lopo
2007-10-22 19:30 ` Orlin Grigorov
2007-10-22 19:38 ` Erik de Castro Lopo
2007-10-22 19:39 ` Jake Donham
2007-10-22 19:44 ` Orlin Grigorov
2007-10-22 19:42 ` Karl Zilles
2007-10-22 19:57 ` Orlin Grigorov [this message]
2007-10-23 7:50 ` Dave Benjamin
2007-10-23 17:17 ` Orlin Grigorov
2007-10-24 12:54 ` Richard Jones
2007-10-24 18:14 ` Karl Zilles
2007-10-24 21:56 ` Sylvain Le Gall
2007-10-22 19:43 ` Re : [Caml-list] " Adrien
2007-10-22 19:59 ` Gordon Henriksen
2007-10-24 12:53 ` Richard Jones
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=b17e12b30710221257o34db8536w3f98246d46d93b91@mail.gmail.com \
--to=ogrigorov@gmail.com \
--cc=caml-list@inria.fr \
--cc=zilles@1969web.com \
/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).