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:30:52 +0100 [thread overview]
Message-ID: <20181111133052.4c4dfbe4@scratchpost.org> (raw)
In-Reply-To: <87wopjua86.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]
Hi Ludo,
On Sun, 11 Nov 2018 12:25:45 +0100
ludo@gnu.org (Ludovic Courtès) wrote:
> > registered - see the "/does_not_exist" workaround) rapid fswatch invocations
> > would waste (potentially enormous amounts of) cpu time and would
> > forkbomb fswatch, shepherd and/or worse things. On the other hand, using
> > fswatch like we do now causes us to lose events. But so does starting fswatch
> > later than the clients. And most fswatch backends (for example the Linux one)
> > can lose events anyway (since the kernel buffer is limited - Linux will then
> > drop events). That's why it always calls the handlers when restarting - just
> > in case.
>
> Uh, not very confidence-inspiring. ;-)
Yeah well, file change notification is surprisingly crappy - especially when
you want it to *always* work. On the other hand typical UNIX :)
> OK that works, but I’m not very comfortable with the approach: normally
> respawns indicate that the service failed unexpectedly, so here we’re
> really abusing the mechanism IMO.
I agree. In the end it would be nicer to get the pipe thing to work or
better yet to have libfswatch bindings or better yet use direvent, aha.
> Another option would be to use Direvent, which supports this and more,
Aha, that looks as if it's intended exactly for this use case! Nice!
I'll try that one next.
> or maybe ‘inotifywatch’ from inotify-tools though it seems to be quite
> similar to fswatch feature-wise.
inotifywatch is Linux-specific. If we want Guix to support the Hurd, BSD,
Windows then it shouldn't be using Linux-specific things. Also, it uses
the same stuff as fswatch under the hood so it has the same limitations.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-11-11 12:31 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 [this message]
2018-11-11 12:50 ` Danny Milosavljevic
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181111133052.4c4dfbe4@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.