From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] upas locking
Date: Thu, 18 Apr 2013 12:12:56 -0400 [thread overview]
Message-ID: <ae0ff31727b2d51406cbd072a29e016e@coraid.com> (raw)
In-Reply-To: <66C08EC8-346E-4BE3-A6EC-815A4FA2E3E3@lsub.org>
On Thu Apr 18 12:10:28 EDT 2013, nemo@lsub.org wrote:
> yes, except that the whole thing
> got worse because one of our servers
> had a lot of memory used due to
> those and we put back the bind for
> tmp.
ramfs -l 10m
(the 9atom version of ramfs does proper accounting to
make this work.)
also, if you're using anything like mdir, you can deliver
the mail and delete it automaticly later.
- erik
prev parent reply other threads:[~2013-04-18 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 9:15 Francisco J Ballesteros
2013-04-18 14:04 ` erik quanstrom
2013-04-18 14:24 ` Francisco J Ballesteros
2013-04-18 14:42 ` erik quanstrom
2013-04-18 14:51 ` Fco. J. Ballesteros
2013-04-18 15:33 ` Charles Forsyth
2013-04-18 15:43 ` lucio
2013-04-18 15:59 ` Francisco J Ballesteros
2013-04-18 16:12 ` erik quanstrom [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=ae0ff31727b2d51406cbd072a29e016e@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
/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).