to add to what Mark said -
P.V.Anthony, mused, then expounded:
> Hi,
>
> I going to built a 1U server which will have the following.
>
> 1. Apache 2
> 2. Lighttpd
Why both web servers?
> 3. qmail
(Can't comment on this, using postfix)
> 4. vpopmail
(Haven't used any pop mail)
> 5. mysql
> 6. postgres
> 7. ruby
> 8. php
> 9. perl
> 10. tinydns
(Have only used this on 32-bit systems)
> 11. pureftpd
> 12. high availblity tools for fail over
>
(Haven't used thes, as I've had no failures)
> The question is which way to go 64bit or 32bit? Which more stable? Which
> is better?
>
I've run a couple of servers, 64-bit, for several years now - one since 2004,
and have had only one minor issue with the LSI MPT driver, but that was fixed
in 2.6.18.
My main uses have been file serving and some mail, along with backing up other
servers via rsnapshot on a daily basis.
Unlike more conservative admins, I run daily updates, with the exception of
critical software - kernel, dhcp, tftp, ftp, and nfs. And those still get
updated after I verify them.
> The reason for this questions is that there are some information on the
> net that says that there is no much difference between them.
> Is that true? Thought that 64bit is always better.
>
There are issues with digital media codecs and web browsers. But these are
servers. Also, note that the vast majority of Unix and Open source tools have
been run 64-bit for several decades on Unix and BSD boxes.
While the amd64 instruction set is a bit newer, and 32-bit code has been run
on millions of boxes, the 64-bit variants are as stable as anything else.
Bob
-
--
[EMAIL PROTECTED] mailing list
