From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ATA next
Date: Thu, 22 Jan 2004 10:53:26 -0500 [thread overview]
Message-ID: <25ce826aaa31b7b821046e74fd4c681b@plan9.bell-labs.com> (raw)
In-Reply-To: <20040122162315.D28365@cackle.proxima.alt.za>
On Thu Jan 22 09:24:50 EST 2004, lucio@proxima.alt.za wrote:
> Now I can run imap4d on the slowest, smallest server in my
> office/network :-) Something tells me either imap4d does not need
> to run on an auth server (it _does_ change identity, doesn't it?)
> or the auth server needs to be considerably more beefy than used
> to be the case a few years ago (don't I recall comments to the
> effect it could run on small 386?).
There's no reason why imapd should run on an auth server.
Lots of services change id (cpu, rx, ssh, ...).
Our auth server has gotten a lot bigger though it doesn't have to be;
we just had some 700 MH zeon's lying around when we needed a bigger
machine..
We use the same machine as an auth server, console server,
and dhcp/bootp/tftp server. Its basicly the stand alone server that
we use to get the rest of the system up after power failures or
file server reboots.
next prev parent reply other threads:[~2004-01-22 15:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 14:23 Lucio De Re
2004-01-22 15:22 ` jmk
2004-01-22 18:19 ` Lucio De Re
2004-01-22 19:13 ` jmk
2004-01-23 5:19 ` Lucio De Re
2004-01-23 9:11 ` Charles Forsyth
2004-01-23 9:37 ` Lucio De Re
2004-01-23 16:38 ` jmk
2004-01-23 16:47 ` C H Forsyth
2004-01-22 15:53 ` David Presotto [this message]
2004-01-22 18:36 ` Lucio De Re
2004-01-22 19:53 ` David Presotto
2004-01-23 5:55 ` [9fans] imap4d operation (Was: ATA next) Lucio De Re
2004-01-23 16:39 ` David Presotto
2004-01-22 20:10 ` [9fans] ATA next David Presotto
2004-01-23 7:11 ` Lucio De Re
2004-01-23 9:00 ` Lucio De Re
2004-01-23 16:37 ` David Presotto
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=25ce826aaa31b7b821046e74fd4c681b@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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).