From: Michael Albinus <michael.albinus@gmx.de>
To: Daniel Jacobowitz <daniel.jacobowitz@gmail.com>
Cc: 66381@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#66381: 29.1; Auto-revert not polling files when notifications are enabled
Date: Sat, 07 Oct 2023 19:59:36 +0200 [thread overview]
Message-ID: <875y3igvp3.fsf@gmx.de> (raw)
In-Reply-To: <CAN9gPaEi7yPgC4cA9fR-TtSmsVg6CoTOZ=bbZFa1gjQA_B1vGA@mail.gmail.com> (Daniel Jacobowitz's message of "Sat, 7 Oct 2023 13:28:02 -0400")
Daniel Jacobowitz <daniel.jacobowitz@gmail.com> writes:
Hi Daniel,
> It's /google/src/<censored>/file.txt, with the mount
> point on /google/src. Mount details:
>
> srcfsd /google/src fuse.srcfsd
> rw,nosuid,nodev,relatime,user_id=125,group_id=0,default_permissions,allow_other
> 0 0
>
> There's no stop notification generated, whether I restart or kill the
> daemon or just umount -l. inotifywait(1) agrees. I've got no idea what
> parts of this may be local kernel behavior versus FUSE in general, but
> I would guess that FUSE in general is more likely.
Yes, likely this is due to the srcfsd FUSE type. I don't use it, so I
cannot test.
Since inotify doesn't deliver IN_IGNORED (and the file-notify `stopped'
event doesn't appear therefore) we cannot do too much. We have no API
which sends heartbeat checks on watched file systems; such a check could
solve the problem. But there are no plans. Your workaround by restarting
global-auto-revert-mode every night might be the best you could use.
Best regards, Michael.
next prev parent reply other threads:[~2023-10-07 17:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 17:13 bug#66381: 29.1; Auto-revert not polling files when notifications are enabled Daniel Jacobowitz
2023-10-07 6:17 ` Eli Zaretskii
2023-10-07 15:15 ` Michael Albinus
2023-10-07 16:14 ` Daniel Jacobowitz
2023-10-07 17:02 ` Michael Albinus
[not found] ` <CAN9gPaEi7yPgC4cA9fR-TtSmsVg6CoTOZ=bbZFa1gjQA_B1vGA@mail.gmail.com>
2023-10-07 17:59 ` Michael Albinus [this message]
2023-10-07 18:14 ` Daniel Jacobowitz
2023-10-07 18:28 ` Eli Zaretskii
2023-10-07 18:41 ` Daniel Jacobowitz
2023-10-07 18:48 ` Daniel Jacobowitz
2023-10-07 19:00 ` Eli Zaretskii
2023-10-08 8:24 ` Michael Albinus
2023-10-08 12:38 ` Michael Albinus
2023-10-09 18:17 ` Daniel Jacobowitz
2023-10-10 18:03 ` Michael Albinus
2023-10-13 12:05 ` Eli Zaretskii
2023-10-15 13:58 ` Michael Albinus
2023-10-16 12:38 ` Eli Zaretskii
2023-10-16 14:29 ` 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=875y3igvp3.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=66381@debbugs.gnu.org \
--cc=daniel.jacobowitz@gmail.com \
--cc=eliz@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.