Hello!
On Sat, Jul 02, 2005 at 11:04:34AM +0800, Jeffrey Lim wrote:
how about the mail store then? I suppose there'll have to be some
coordinated (and thread-friendly) back-end mail store in place for
these front-end mail servers (*i'm assuming simplistic load-balancing
here - at the tcp level,
I'm late to the game... but why not split the load over a number
of servers? Using carp for reduncancy, rdr/round-robin and/or hash,
you should be able to spread the load some.
--Toby.
On Wednesday, June 29, Jeffrey Lim wrote:
On 6/29/05, Matt Juszczak [EMAIL PROTECTED] wrote:
Just spoke with
I concur. mail load is ideally suited for dividing up
amongst multiple machines (with then multiple i/o busses, etc. etc.).
I far prefer this method to the one big machine method.
-Bob
* Tobias Weingartner [EMAIL PROTECTED] [2005-07-01 10:11]:
I'm late to the game...
how about the mail store then? I suppose there'll have to be some
coordinated (and thread-friendly) back-end mail store in place for
these front-end mail servers (*i'm assuming simplistic load-balancing
here - at the tcp level, rather than at the application level, or
splitting via userid, so that
Can you live with just one processor? You would probably have much
better luck with SMP disabled.
Joe
On 6/28/05, Matt Juszczak [EMAIL PROTECTED] wrote:
Hi all,
Some of you have read my posts from the previous few days but I am really
stuck right now. Sorry if this is repeated information
Either, I think in general SMP is tough to get stable. People with
more experience will hopefully reply and explain in more detail. For
now I, personally, would disable smp on freebsd just to keep it
stable.
I just dont know if this will keep it stable or not. Others are reporting
that the
On 6/28/05, Matt Juszczak [EMAIL PROTECTED] wrote:
My boss really wants to run SMP. He [...] thinks that a single 3 ghz
with 4 gb RAM couldn't handle our mail server [...]
To avoid making CLM's, you should realise these lists are archived indefinitely.
If things are crashing twice a day and
According to
http://www.freebsd.org/security/
the current estimated EOL for 4.11 is January 31, 2007
That said, since you think IPF is causing problems, have your tried disabling
IPF and running either ipfilter or PF (or doing the filtering on a dedicated
firewall box)?
--Matt
Yep, I
According to
http://www.freebsd.org/security/
the current estimated EOL for 4.11 is January 31, 2007
That said, since you think IPF is causing problems, have your tried
disabling IPF and running either ipfilter or PF (or doing the filtering on
a dedicated firewall box)?
--Matt
--On
We're running FreeBSD at work on our main mail server, which is now
crashing 2 times per day. I need to find a new solution soon, or I
could risk losing my job which would really stink.
http://www.dragonflybsd.org/
From Wikipedia, the free encyclopedia.
In computing, the DragonFly BSD
10 matches
Mail list logo
