From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 33265@debbugs.gnu.org
Subject: [bug#33265] [WIP RFC v4] services: Add file system monitoring service.
Date: Sun, 11 Nov 2018 13:50:33 +0100 [thread overview]
Message-ID: <20181111134811.7d48b621@scratchpost.org> (raw)
In-Reply-To: <87wopjua86.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
> Another option would be to use Direvent
I've read through direvent 5.1 now and:
(1) It supports only watching entire directories. OK I guess, especially
since the client can specify basename filters to be applied, so if you
want to watch individual files you can, using a strange configuration
(something like: path $(dirname $file), file $(escape-regex $(basename $file))).
(2) It doesn't notify the client on inotify queue overflow. *shakes head*
(genev_xlat does not translate IN_Q_OVERFLOW)
(fswatch does notify the client on inotify queue overflow)
Whoever doesn't handle inotify queue overflow uses the kernel API incorrectly -
it's not going to be reliable.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-11-11 12:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 3:18 [bug#33265] [WIP RFC] services: Add file system monitor service Danny Milosavljevic
2018-11-05 3:45 ` [bug#33265] [WIP RFC v2] " Danny Milosavljevic
2018-11-05 3:51 ` [bug#33265] [WIP RFC v3] services: Add file system monitoring service Danny Milosavljevic
2018-11-05 9:16 ` swedebugia
2018-11-05 9:41 ` [bug#33265] [WIP RFC v4] " Danny Milosavljevic
2018-11-10 22:19 ` Ludovic Courtès
2018-11-11 0:12 ` Danny Milosavljevic
2018-11-11 0:13 ` Danny Milosavljevic
2018-11-11 11:25 ` Ludovic Courtès
2018-11-11 12:30 ` Danny Milosavljevic
2018-11-11 12:50 ` Danny Milosavljevic [this message]
2018-11-11 13:22 ` Ludovic Courtès
2018-11-05 9:36 ` [bug#33265] [WIP RFC] services: Add file system monitor service Clément Lassieur
2018-11-11 0:15 ` Danny Milosavljevic
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181111134811.7d48b621@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=33265@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).