From: Madhu <enometh@meer.net>
To: michael.albinus@gmx.de
Cc: emacs-devel@gnu.org
Subject: Re: tramp "too many open files" [Re: bug#56606
Date: Tue, 21 Mar 2023 00:17:21 +0530 (IST) [thread overview]
Message-ID: <20230321.001721.167098091969271495.enometh@meer.net> (raw)
In-Reply-To: <87ttyfzcpf.fsf@gmx.de>
* Michael Albinus <87ttyfzcpf.fsf @gmx.de>
Wrote on Mon, 20 Mar 2023 16:04:12 +0100
> Madhu <enometh@meer.net> writes:
>> The #56606 is archived and this may be unrelated and related to tramp,
>> but I wanted to note I encoutered something similar on recent master
>> (GNU Emacs 30.0.50 (build 2, x86_64-pc-linux-gnu, X toolkit, cairo
>> version 1.16.0, Xaw3d scroll bars) of 2023-03-18) native compilation.
>
> I might be wrong, but likely, bug#56606 is unrelated.
Thanks for your note, Sorry for the false alarm.
>
> Hmm. tramp-archive.el uses th GVFS file system to read a file
> archive. GVFS in this case uses libarchive(3).
I notice my gvfsd is not compiled with libarchive.
>> Of course I could do nothing but kill the process. I updated mew to 6.9
>> and tried the sequence again in a fresh emacs, but wasn't able to
>> reproduce this (but hit a vertico bug instead)
>>
>> If this looks familiar, or if someone has a clue about it, please tell
>> me. Maybe I should a bug report under the `tramp' product if I hit it
>> again.
>
> What I could imagine is, that Emacs has many of the files open from the zip
> file. However, mew shouldn't use tramp-archive.el ...
Ah, I might have made a mistake when entering the filename: by adding
"foo.zip/" when saving the file (it uses read-file-name)
> Well, I'm not familiar with mew. Could you please write a bug report,
> which contains a recipe starting with "emacs -Q", and which tells how to
> reach the point when the error appeared as reported above. The recipe is
> also good when it doesn't show the error; I want to use it in order to
> see how tramp-archive.el comes into play.
Usually I run without a system dbus (but with a session dbus for
emacs). tramp-archive disables itself when it finds it cannot connect
to a system dbus, so I was protected from it being triggered. (btw if
the situation changes, and a system dbus comes up later, it has to be
initialized explicitly with (dbus-init-bus :system))
I think I happened to have a system dbus when I triggered the
error. tramp found a gvfs and gvfs-fuse process, but it wouldn't have
worked because gvfds is not linked with libarchive.
So far I've not able to reproduce the error and am not sure. When I
try to trigger it with a filename with like /tmp/foo.zip/sle.txt, it
just says that there is no such directory.
[I'll try to compile gvfsd with libarchive and try again later, but it
will take some time to unscrew and fix the gentoo config: I have to
update libarchive, and that requires undoing some upstream e2fsprogs
decisions.]
next prev parent reply other threads:[~2023-03-20 18:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86ilnwafso.fsf@stephe-leake.org>
[not found] ` <handler.56606.B.165800822832001.ack@debbugs.gnu.org>
[not found] ` <86a6989itv.fsf@stephe-leake.org>
[not found] ` <8335f0qbvn.fsf@gnu.org>
[not found] ` <831qujrjnm.fsf@gnu.org>
[not found] ` <86h73ex91m.fsf@stephe-leake.org>
[not found] ` <83k089omhb.fsf@gnu.org>
2023-03-20 13:31 ` tramp "too many open files" [Re: bug#56606 Madhu
2023-03-20 14:58 ` Thierry Volpiatto
2023-03-20 15:20 ` Michael Albinus
2023-03-20 16:57 ` Thierry Volpiatto
2023-03-20 17:56 ` Michael Albinus
2023-03-21 5:55 ` Thierry Volpiatto
2023-03-21 9:22 ` Michael Albinus
2023-03-21 13:43 ` Thierry Volpiatto
2023-03-21 15:17 ` Michael Albinus
2023-03-21 17:19 ` Thierry Volpiatto
2023-03-20 15:04 ` Michael Albinus
2023-03-20 18:47 ` Madhu [this message]
2023-03-21 9:30 ` Michael Albinus
2023-03-25 23:23 ` {Spam?} " Madhu
2023-03-26 18:56 ` tramp "too many open files" Michael Albinus
2023-05-14 5:44 ` Build failure: " Madhu
2023-05-14 7:10 ` Michael Albinus
2023-05-14 10:00 ` {Spam?} " Madhu
2023-05-14 11:24 ` 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=20230321.001721.167098091969271495.enometh@meer.net \
--to=enometh@meer.net \
--cc=emacs-devel@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).