all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 33265@debbugs.gnu.org
Subject: [bug#33265] [WIP RFC v4] services: Add file system monitoring service.
Date: Sun, 11 Nov 2018 14:22:39 +0100	[thread overview]
Message-ID: <87a7mfu4tc.fsf@gnu.org> (raw)
In-Reply-To: <20181111134811.7d48b621@scratchpost.org> (Danny Milosavljevic's message of "Sun, 11 Nov 2018 13:50:33 +0100")

Hello Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> Whoever doesn't handle inotify queue overflow uses the kernel API incorrectly -
> it's not going to be reliable.

It seems that inotify and reliability don’t go together well anyway:

  http://wingolog.org/archives/2018/05/21/correct-or-inotify-pick-one

So I don’t know if what you describe is a showstopper for Direvent
specifically, or if it’s just that things aren’t going to work
“reliably” anyway.

WDYT?

Ludo’.

  reply	other threads:[~2018-11-11 13:23 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
2018-11-11 13:22               ` Ludovic Courtès [this message]
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=87a7mfu4tc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33265@debbugs.gnu.org \
    --cc=dannym@scratchpost.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.