git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Strange "beagle" interaction..

From
David Brown <git@davidb.org>
Date
Nov 13, 2007, 21:49 UTC
Message-ID
<20071113214934.GA30950@old.davidb.org>
In-Reply-To
<9e4733910711131344t381b939dg47b5e078c52be3b2@mail.gmail.com>
On Tue, Nov 13, 2007 at 04:44:33PM -0500, Jon Smirl wrote:
Show 5 quoted lines
>A better solution would be for the kernel to log inotify events to
>disk in a manner that survives reboots. When Beagle starts it would
>locate its last checkpoint and then process the logged inotify events
>from that time forward. This inotify logging needs to be bullet proof
>or it will mess up your Beagle index.

Perhaps something similar to FsEvents on OSX which is a daemon that interfaces with the OS to record this very information.

It only works across clean reboots, but it does work there. Do a bad shutdown, and your next backup or index take a long time to go scan everything.

It would also be wonderful to have this for backups as well.
Dave
Previous: Jon SmirlNext: J. Bruce Fields
Message 6 of 9 in “Strange "beagle" interaction..”
  1. Linus TorvaldsNov 13, 2007
  2. J. Bruce FieldsNov 13, 2007
  3. J. Bruce FieldsNov 13, 2007
  4. Linus TorvaldsNov 13, 2007
  5. Jon SmirlNov 13, 2007
  6. David BrownNov 13, 2007
  7. J. Bruce FieldsNov 13, 2007
  8. Jon SmirlNov 13, 2007
  9. Mike HommeyNov 13, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.