Koozali.org: home of the SME Server

Minimum requirements

tzenko

Minimum requirements
« on: June 07, 2003, 08:34:33 PM »
what is the slowest computer I can install e-smith? I have some old PCs, but i have to decide wich one... or I need a new one?


tzenko

Re: Minimum requirements
« Reply #2 on: June 07, 2003, 10:23:33 PM »
Thanks!

Steve

Re: Minimum requirements
« Reply #3 on: June 07, 2003, 11:36:22 PM »
5.1.2 will install & run on a P75 with 16meg ram although the web interface will be slow. 5.6 requires more ram, it then depends on if its a home installation or you intend to serve a number of users.

Dave Liquorice

Re: Minimum requirements
« Reply #4 on: June 08, 2003, 01:30:12 AM »
I've just put 5.6 onto a P133 with 48M RAM as a play machine. It runss but any of the web based stuff is un-useable, indeed httpd-admin and httpd-e-smith failed to load so I've disabled them in the configuration file. I guess if I threw more memory at it, it would be a lot happier but it serves my needs a test bed.

Ray Mitchell

Re: Minimum requirements
« Reply #5 on: June 08, 2003, 11:38:19 AM »
Dave
If you throw in just a little bit more RAM (say 64Mb as a minimum) it should run OK (albeit slowly) with v5.6. I have a P133 64Mb and it runs without needing to turn services off, but it does not do very much (light duty).

Regards
Ray

Wes

Re: Minimum requirements
« Reply #6 on: June 08, 2003, 05:27:59 PM »
I ran on a PII 233Mhz with 128MB RAM quite successfully.  It was intended to be a file server to a 6 client mini-lab, then they unexpectedly choughed up the funds for a Ghz server.  The HTML interface was slow as molasses but as a file server you could not tell the difference at the client end.

Peter Edwards

Re: Minimum requirements
« Reply #7 on: June 26, 2003, 11:50:00 AM »
Can happily report that I have 5.6 running on a PII400, 128Mb RAM. Serves 20 people with file/mail/ftp support. Coughed and spluttered a bit when I had https running on webmail (marketing types like attaching huge pdf's to everything) So I switched it back down to http and it chugs away happily.