On Mon, 25 Oct 2010, Kenton Varda wrote:
|On Mon, Oct 25, 2010 at 1:54 AM, Igor V. Ruzanov wrote:
|
|> I thought so too but was not sure about his problem. With
|> kqueue()/kevent() we can monitor every open file descriptor. So how many
|> files are laid down in the directory tree, 100, 1000, 150
Ivan Voras wrote:
> Short answer: no.
>
> Long answer: There should be. There were past discussions on writing
> such a facility to e.g. receive events for all files on per-mountpoint
> basis (which you could filter...), but we're not there yet.
Thanks! That answers my question. I'll find some s
On Mon, Oct 25, 2010 at 1:54 AM, Igor V. Ruzanov wrote:
> I thought so too but was not sure about his problem. With
> kqueue()/kevent() we can monitor every open file descriptor. So how many
> files are laid down in the directory tree, 100, 1000, 15000? In every
> such way its possible to write o
On 10/25/10 03:05, Kenton Varda wrote:
> Hi all,
>
> I am trying to write some code which monitors a possibly-large directory
> tree for changes. Specifically, it's a build system, and I want it to
> automatically start rebuilding whenever I modify a source file.
>
> So far the approach I've tak
On Mon, 25 Oct 2010, Erik Trulsson wrote:
|On Mon, Oct 25, 2010 at 10:48:58AM +0400, Igor V. Ruzanov wrote:
|> On Sun, 24 Oct 2010, Kenton Varda wrote:
|>
|> |That doesn't answer my question. I'm not even using make. I could write a
|> |few thousand words describing exactly what I'm trying to d
On Mon, Oct 25, 2010 at 10:48:58AM +0400, Igor V. Ruzanov wrote:
> On Sun, 24 Oct 2010, Kenton Varda wrote:
>
> |That doesn't answer my question. I'm not even using make. I could write a
> |few thousand words describing exactly what I'm trying to do and why it does,
> |in fact, make sense, but i
On Sun, 24 Oct 2010, Kenton Varda wrote:
|That doesn't answer my question. I'm not even using make. I could write a
|few thousand words describing exactly what I'm trying to do and why it does,
|in fact, make sense, but it's really beside the point. I just want to know
|if there is any scalable
large directory tree for
changes. Is there?
On Sun, Oct 24, 2010 at 9:46 PM, Robert Bonomi wrote:
> > From owner-freebsd-questi...@freebsd.org Sun Oct 24 22:17:42 2010
> > Date: Sun, 24 Oct 2010 18:05:34 -0700
> > From: Kenton Varda
> > To: freebsd-questions@freebsd.or
> From owner-freebsd-questi...@freebsd.org Sun Oct 24 22:17:42 2010
> Date: Sun, 24 Oct 2010 18:05:34 -0700
> From: Kenton Varda
> To: freebsd-questions@freebsd.org
> Subject: EVFILT_VNODE doesn't scale to large directory trees?
>
> Hi all,
>
> I am trying to
Hi all,
I am trying to write some code which monitors a possibly-large directory
tree for changes. Specifically, it's a build system, and I want it to
automatically start rebuilding whenever I modify a source file.
So far the approach I've taken is to use EVFILT_VNODE to watch every file
and dir
10 matches
Mail list logo
