public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John McCutchan <ttb@tentacle.dhs.org>
To: Dale Blount <linux-kernel@dale.us>
Cc: Robert Love <rml@novell.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] inotify 0.22
Date: Mon, 04 Apr 2005 18:21:22 -0400	[thread overview]
Message-ID: <1112653282.11281.2.camel@vertex> (raw)
In-Reply-To: <1112647855.520.20.camel@dale.velocity.net>

On Mon, 2005-04-04 at 16:50 -0400, Dale Blount wrote:
> Will inotify watch directories recursively?  A quick browse through the
> source doesn't look like it, but I very well could be wrong.  Last I
> checked, dnotify did not either.  I am looking for a way to synchronize
> files in as-real-as-possible-time when they are modified.  The ideal
> implementation would be a kernel "hook" like d/inotify and a client
> application that watches changes and copies them to a remote server for
> redundancy purposes.   A scheduled rsync works decently, but has a lag
> time of 2-3 (or more) hours on certain files on a large filesystem.
> Will inotify work for this, or does someone else have another
> recommended solution to the problem?

This problem is solved really well by inotify. But inotify will not
watch directories recursively for you. You can easily spider your way
down the path yourself adding a watch for each directory you encounter.
This is how beagle works, which has the same needs as your problem.

-- 
John McCutchan <ttb@tentacle.dhs.org>

  parent reply	other threads:[~2005-04-04 22:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 20:02 [patch] inotify 0.22 Robert Love
2005-04-04 20:18 ` [patch] inotify 0.22 for 2.6.12-rc1-mm4 Robert Love
2005-04-04 20:50 ` [patch] inotify 0.22 Dale Blount
2005-04-04 21:04   ` Robert Love
2005-04-04 22:21   ` John McCutchan [this message]
2005-04-05  9:26 ` Martin Schlemmer
2005-04-05 16:56 ` [patch] updated " Robert Love
2005-04-05 16:59   ` [patch] updated inotify 0.22 for 2.6-mm Robert Love

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=1112653282.11281.2.camel@vertex \
    --to=ttb@tentacle.dhs.org \
    --cc=linux-kernel@dale.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.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