unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Troy de Freitas <me@ntdef.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 53191@debbugs.gnu.org
Subject: bug#53191: 29.0.50; file-notify-add-watch fails for socket files on MacOS
Date: Sat, 15 Jan 2022 10:49:27 -0600	[thread overview]
Message-ID: <E6F0AE41-467B-4BA9-8FCA-E0FBDF61E2BA@ntdef.com> (raw)
In-Reply-To: <877db1ys58.fsf@gmx.de>

Hi Michael, 

Thanks for looking into this. Actually, all I wanted was to be able to see when the socket file was deleted. 

Regards,
Troy de Freitas

> On Jan 15, 2022, at 8:45 AM, Michael Albinus <michael.albinus@gmx.de> wrote:
> 
> Michael Albinus <michael.albinus@gmx.de> writes:
> 
> Hi Troy,
> 
>> Thanks for the report. The incrimed behavior is due to unconditional
>> using of the EVFILT_VNODE filter, calling EV_SET in
>> Fkqueue_add_watch. This requires a file descriptor.
>> 
>> I'll investigate, whether another filter, like EVFILT_READ, is better
>> suited for sockets, using a sockfd. This might take some days, though.
> 
> I'm sorry, but it seems that EV_SET requires a file descriptor. I
> couldn't find a way to pass the socket file otherwise but via open(),
> which doesn't work on *BSD-like systems, as you have analyzed.
> 
> What is your use case to supervise a socket file? You can't get more
> information except that the file is deleted. And this you get also if
> you monitor the parent directory.
> 
>>> - Troy
> 
> Best regards, Michael.






  reply	other threads:[~2022-01-15 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 16:22 bug#53191: 29.0.50; file-notify-add-watch fails for socket files on MacOS Troy de Freitas
2022-01-12  9:01 ` Michael Albinus
2022-01-15 14:45   ` Michael Albinus
2022-01-15 16:49     ` Troy de Freitas [this message]
2022-01-15 17:37       ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E6F0AE41-467B-4BA9-8FCA-E0FBDF61E2BA@ntdef.com \
    --to=me@ntdef.com \
    --cc=53191@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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/emacs.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).