From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] ftpfs no-cache patch
Date: Wed, 14 Feb 2018 14:12:18 +0000 [thread overview]
Message-ID: <1518617538.2866478.1270619816.5DB5EB4A@webmail.messagingengine.com> (raw)
In-Reply-To: <9BDA4290D351360B58546007996BD00F@sphericalharmony.com>
On Tue, Feb 13, 2018, at 8:09 PM, mycroftiv@sphericalharmony.com wrote:
> Summary: ftpfs caching behavior seems mostly undesirable. This patch
> eliminates caching by default and allows the previous behavior to be
> restored with a -h flag.
>
> Details: the ftpfs manpage currently states "Ftpfs caches files and
> directories. A directory will fall from the cache after 5 quiescent
> minutes or if the local user changes the directory by writing or
> removing a file." - but I believe this is not accurate. According to
> my testing, there is no time-based directory cache expiry. The
> ftpfs.h file does define an ISOLD macro that would fit the manpage,
> but a grep reveals that the ISOLD macro is never used anywhere in the
> current code. The cache can be cleared by using the special
> .flush.ftpfs directory entry.
I support this. I've occasionally used ftpfs to transfer files from or to (or browse) my Android devices. Even in that light usage, having to manually flush was a big pain. I wrote a script, called it "fff", so I could flush it with just that one word, but but it was still a big pain. In the end, I configured rc-httpd to serve a big chunk of my homedir to my local network only, and used the web browser on my phone.
prev parent reply other threads:[~2018-02-14 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 20:09 mycroftiv
2018-02-14 14:12 ` Ethan Grammatikidis [this message]
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=1518617538.2866478.1270619816.5DB5EB4A@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.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.
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 NNTP newsgroup(s).