From: Mark Alexander <marka@pobox.com>
To: Shadowfirebird <shadowfirebird@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Slow opening of threads?
Date: Fri, 22 Oct 2010 12:28:01 -0400 [thread overview]
Message-ID: <1287764701-sup-6487@r61> (raw)
In-Reply-To: <1287752134-sup-9563@blake>
Excerpts from Shadowfirebird's message of Fri Oct 22 09:03:15 -0400 2010:
> Interesting that you should mention that, because I have an
> encrypted $HOME (bad choice at Ubuntu install time -- ::shrug:: ). I
> suppose it might apply the other way around, too.
That could do it. It would mean your .sup directory (and the Xapian
index) would be on ecryptfs, which could be slow.
In my case, my home directory is not encrypted. I only put
work-related stuff (e.g., email) on an encrypted directory
($HOME/Private) that I set up initially with ecryptfs-setup-private.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-10-22 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 9:23 Shadowfirebird
2010-10-22 10:40 ` Amadeusz Żołnowski
2010-10-22 11:48 ` Shadowfirebird
2010-10-22 13:09 ` Moritz Wilhelmy
2010-10-22 18:02 ` Shadowfirebird
2010-10-22 23:32 ` Moritz Wilhelmy
2010-10-22 11:04 ` Gaute Hope
2010-10-22 11:16 ` Philipp Überbacher
2010-10-22 12:21 ` Ben Walton
2010-10-22 12:38 ` Mark Alexander
2010-10-22 13:03 ` Shadowfirebird
2010-10-22 16:28 ` Mark Alexander [this message]
2010-10-22 17:19 ` Sascha Silbe
2010-10-22 19:56 ` Shadowfirebird
2010-10-23 8:28 ` Sascha Silbe
2010-10-23 10:42 ` Shadowfirebird
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=1287764701-sup-6487@r61 \
--to=marka@pobox.com \
--cc=shadowfirebird@gmail.com \
--cc=sup-talk@rubyforge.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