public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcin Krol <mrkafk@gmail.com>
To: Martin Steigerwald <ms@teamix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: inotify limits - thousands (tens of thousands?) of watches
Date: Wed, 20 May 2009 14:16:29 +0200	[thread overview]
Message-ID: <4A13F49D.7000905@gmail.com> (raw)
In-Reply-To: <200905201322.15075.ms@teamix.de>

Martin Steigerwald wrote:
> Hmmm, I think you could just run a rsync periodically. It might even be faster 
> detecting changed files. 

I beg to differ on this: rsync does quite intensive (in terms of disk 
activity and CPU activity) comparisons at the beginning of 
synchronization. It's pretty light later, true, but running rsync every 
few minutes on entire /home is IMO out of question.

> I wrote a ruby script using libinotify-ruby which does just that. I only syncs 
> on demand tough. I.e. when someplace places a special sync file in a watched 
> directory.

> That script is running productively for well over a year now.

Good to know the idea is not totally off the wall.. Thanks.

Anyway, I'll try using fsnotify / fanotify.

My main gripe with it, though, is that it is not in the mainline kernel, 
and thus in all probability it is not tested as widely as inotify.

Are there any chances for its inclusion in the near future?

Regards,
mk

  reply	other threads:[~2009-05-20 12:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20  9:26 inotify limits - thousands (tens of thousands?) of watches Marcin Krol
2009-05-20 10:04 ` Matthias Kaehlcke
2009-05-20 10:12 ` Tvrtko Ursulin
2009-05-20 11:22 ` Martin Steigerwald
2009-05-20 12:16   ` Marcin Krol [this message]
2009-05-20 12:48     ` Martin Steigerwald
2009-05-20 12:58     ` Martin Steigerwald
2009-05-20 13:58 ` hooanon05

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=4A13F49D.7000905@gmail.com \
    --to=mrkafk@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ms@teamix.de \
    /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