>From personal experience this is a tad much for one machine. DNS can
fill up some memory w/ cache and is a constant hit. Really should be
its own 486 or so w/ some memory tossed in. Shell services can be
dangerous, and a user could easily peg out a system. We run a shell
machine, a dns server,
On Sat, 3 Jan 1998, Shaleh wrote:
> >From personal experience this is a tad much for one machine. DNS can
> fill up some memory w/ cache and is a constant hit. Really should be
> its own 486 or so w/ some memory tossed in. Shell services can be
> dangerous, and a user could easily peg out a sys
>From personal experience this is a tad much for one machine. DNS can
fill up some memory w/ cache and is a constant hit. Really should be
its own 486 or so w/ some memory tossed in. Shell services can be
dangerous, and a user could easily peg out a system.
--
TO UNSUBSCRIBE FROM THIS MAILING
I'm running a Debian 1.3.1 system and find the machine, when put into our
production environment here, after a little while causes the machine's
load to rise, and keep on going. It was so bad it got up to 150+ once. At
any ratI ran top one time and nothing was using any large amount of CPU,
nor was
4 matches
Mail list logo
