all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21432@debbugs.gnu.org, tsdh@gnu.org
Subject: bug#21432: 25.0.50; file-notify-rm-watch (inotify) errors if watched dir is deleted
Date: Sat, 12 Sep 2015 20:09:52 +0200	[thread overview]
Message-ID: <87zj0rh5lb.fsf@gmx.de> (raw)
In-Reply-To: <83fv2jbrkm.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 12 Sep 2015 18:11:37 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> I've checked, all three Emacs libraries inotify, gfilenotify and
>> w32notify return an error when *-rm-watch detects a problem.
>> `file-notify-rm-watch' could propagate this error. The manual
>> shall be extended then.
>
> But the issue comes up before you remove the watch.  You have a watch
> that is in fact inoperable, but the application might not know about
> that, or get hit by a signal out of nowhere.
>
> So I think having a validation function is a good idea.

Yes. I've started to write a prototype for inotify.c, will show when it
works (slow progress, you know :-( )

>> At least inotify removes a watch internally, when it detects that the
>> file/directoy to be watched does not exist any longer.
>
> That's a bug, IMO: it shouldn't.

I tend to agree. Will check further with inotify.c, but likely we should
discard this "feature".

>> Shall we unify this behaviour? I'm not in favor of the inotify
>> behaviour, the libraries shall raise a final signal instead that the
>> watch is stopped. filenotify shall propagate this then, for example as
>> `stopped' event or something like this.
>
> I don't think you can easily raise a signal.  I think we should
> provide a validate function for the applications to use.

At least for inotify, it is built-in. It sends the `ignored' signal when
the directory or file being watch disappears, due to a delete, rename, or
unmount, whatever:

--8<---------------cut here---------------start------------->8---
(progn
  (trace-function 'file-notify-handle-event)
  (write-region "any text" nil "/tmp/xxx")
  (inotify-add-watch "/tmp/xxx" 'all-events 'ignore)
  (delete-file "/tmp/xxx"))

======================================================================
1 -> (file-notify-handle-event (file-notify (1 (attrib) nil 0) ignore))
1 <- file-notify-handle-event: nil
======================================================================
1 -> (file-notify-handle-event (file-notify (1 (delete-self) nil 0) ignore))
1 <- file-notify-handle-event: nil
======================================================================
1 -> (file-notify-handle-event (file-notify (1 (ignored) nil 0) ignore))
1 <- file-notify-handle-event: nil
--8<---------------cut here---------------end--------------->8---

For gfilenotify it isn't such simple, unfortunately.

Best regards, Michael.





  reply	other threads:[~2015-09-12 18:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  6:36 bug#21432: 25.0.50; file-notify-rm-watch (inotify) errors if watched dir is deleted Tassilo Horn
2015-09-08  7:47 ` Michael Albinus
2015-09-08  8:11   ` Tassilo Horn
2015-09-08 15:51   ` Eli Zaretskii
2015-09-08 15:49 ` Eli Zaretskii
2015-09-08 16:01   ` Michael Albinus
2015-09-12 10:18     ` Michael Albinus
2015-09-12 15:11       ` Eli Zaretskii
2015-09-12 18:09         ` Michael Albinus [this message]
2015-09-13 19:23           ` Michael Albinus
2015-09-14  6:08             ` Tassilo Horn
2015-09-14  7:08               ` Eli Zaretskii
2015-09-14  7:40                 ` Tassilo Horn
2015-09-14  7:56                   ` Tassilo Horn
2015-09-14 13:22                     ` Eli Zaretskii
2015-09-14 20:23                       ` Michael Albinus
2015-09-15  7:38                         ` Eli Zaretskii
2015-09-15  8:00                           ` Michael Albinus
2015-09-15  8:22                             ` Eli Zaretskii
2015-09-15 11:54                               ` Michael Albinus
2015-09-15 12:51                                 ` Eli Zaretskii
2015-09-15 12:56                                   ` Michael Albinus
2015-09-16 14:45                                   ` Michael Albinus
2015-09-16 17:08                                     ` Eli Zaretskii
2015-09-16 17:26                                       ` Michael Albinus
2015-09-16 17:55                                         ` Eli Zaretskii
2015-09-16 18:28                                           ` Michael Albinus
2015-09-15  5:53                       ` Tassilo Horn
2015-09-14  7:35         ` Eli Zaretskii
2015-09-14  7:37           ` Michael Albinus
2015-09-15 13:02           ` Michael Albinus
2015-09-15 13:56             ` Eli Zaretskii
2015-09-16 13:54               ` Michael Albinus
2015-09-20 17:23 ` Michael Albinus
2015-09-20 19:19   ` Eli Zaretskii
2015-09-21 13:40     ` Michael Albinus

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=87zj0rh5lb.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=21432@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=tsdh@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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.