Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: Stephan Trajkoff <stephan@itp.bg>
Cc: Matthew Wilcox <willy@debian.org>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] STI framebuffer and PINE
Date: Mon, 15 Jul 2002 15:31:36 +0200	[thread overview]
Message-ID: <20020715133136.GR12241@charite.de> (raw)
In-Reply-To: <3D32CDA9.2050403@itp.bg>

On Mon, Jul 15, 2002 at 04:27:05PM +0300, Stephan Trajkoff wrote:

> My K class server works perfect with 240 users for mail.
> this server has apache, squid, pine,qmail

Quite nice.

> 4 cpu with 120mhz, 512mb ramm, 18GB HDD, what more???

* squid doesn't actually use more than one processor (state machine!)
* qmail is I/O bound.

Only a new Apache2 would benefit from a multi processor box.
If you replace qmail with postfix, you might speed things up a bit.

> my linux in my ISP is with P3 800Mhz, 256mb ram, 20GB HDD wtih apache, 
> mysql, radius, routing, shapers.
> Why did you call me lunatic???

Because Linux isn't really as stable on HPPA as on say Alpha or x386!

> Come here and see motor scooter 50cc runing at 80km/h:)))

I bet it's against the law :)

-- 
Ralf Hildebrandt (Im Auftrag des Referat V A)   Ralf.Hildebrandt@charite.de
Charite Campus Virchow-Klinikum                 Tel.  +49 (0)30-450 570-155
Referat V A - Kommunikationsnetze -             Fax.  +49 (0)30-450 570-916
Why you can't find your system administrators:
Went to Stop&Go to get ANOTHER case of insert favorite caffinated beverage here 

  reply	other threads:[~2002-07-15 13:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-14  9:17 Re: [parisc-linux] STI framebuffer and PINE Stephan Trajkoff
2002-07-14  9:39 ` [parisc-linux] Re: " Martin Schulze
2002-07-14  9:50 ` [parisc-linux] " Ralf Hildebrandt
2002-07-14 11:32   ` Ralf Hildebrandt
2002-07-15 13:20 ` Matthew Wilcox
2002-07-15 13:27   ` Stephan Trajkoff
2002-07-15 13:31     ` Ralf Hildebrandt [this message]
2002-07-15 14:37   ` Alan Cox
2002-07-15 13:33     ` Ralf Hildebrandt
2002-07-15 13:39     ` Matthew Wilcox
2002-07-15 14:57       ` Alan Cox
2002-07-15 13:55         ` Matthew Wilcox
2002-07-15 15:42           ` Alan Cox
2002-07-15 21:50       ` Grant Grundler
2002-07-16  7:29         ` Matthieu Delahaye
2002-07-16 10:12           ` testimonials (was Re: [parisc-linux] STI framebuffer and PINE) Thibaut VARENE
2002-07-16 11:36           ` [parisc-linux] STI framebuffer and PINE Matthew Wilcox
2002-07-15 23:03     ` [parisc-linux] 2.4.19 merge Grant Grundler
2002-07-16  0:23       ` Alan Cox
2002-07-15 23:30         ` Rafael E. Herrera
2002-07-16 10:31           ` Alan Cox
2002-07-16 15:17             ` Randolph Chung
2002-07-16  6:40         ` Grant Grundler
  -- strict thread matches above, loose matches on Subject: below --
2002-07-14  6:52 [parisc-linux] STI framebuffer and PINE Stephan Trajkoff
2002-07-14  8:12 ` Ralf Hildebrandt
2002-07-15 12:55   ` Matthew Wilcox
2002-07-15 13:24     ` Ralf Hildebrandt
2002-07-15 13:28       ` Stephan Trajkoff
2002-07-14 10:56 ` Helge Deller

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=20020715133136.GR12241@charite.de \
    --to=ralf.hildebrandt@charite.de \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=stephan@itp.bg \
    --cc=willy@debian.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