My server when it did a lot of updates, i did a yum clean all and then yum update -y then all was well...
My server when it did a lot of updates, i did a yum clean all and then yum update -y then all was well...
You didn't want to listen to the advice here about running Fedora on a production server so voel maar boetie. There is some solid advice given in this tread and I stand behind not running Fedora as a Production server. Get Centos.
CentOS is OK I have used it before on the amazon cloud. If I do experience show stopping issues I may consider it. The problem with most sysadmins is that you guys don't like to experiment. Distributions like Fedora can be very stable, they go through rigorous testing from people. If you take the time to learn whats going on you can configure a really solid environment and learn a thing or 2 in the process.
A distribution shows what its really made of when it is stress tested under the load of a production environment.
Actually, we do. The difference is, we don't experiment on production servers, if we can help it.
And that's I don't use Fedora on production servers. It has proven itself to be immature and unpredictable. I'm not saying it's a bad distro, but there's a significant difference between it and RHEL.
I like to sleep at night - not "learn a thing or 2" in the dead of night.
My flickr
Last edited by koffiejunkie; 03-08-2012 at 01:26 PM.
My flickr
My choice:
CentOS for web hosting servers.
Debian for running specific applications
BSD (for ZFS) for backup servers
“I believe Ayn Rand's first love poem went: Roses are red, violets are blue, finish this poem yourself you dependent parasite".”
Colbert
Odd, I have them the other way around. Well, at work we use RHEL, so I have no choice, but I prefer Debian for small solutions for most applications. RHEL/CentOS still doesn't have a way to make Apache speak to php-fpm out of the box, and probably won't in RHEL7/CentOS7 either. Of course, at work I build the packages for this, but it means I have to maintain it, and I can't complain to our Red Hat account manager if I stumble upon bugs.
I'm liking that idea too. I've tried the two solutions for ZFS under linux (Fuse and zfsonlinux) - I don't recommend either for anything more than tinkering with it to get to know it. It's really flakey.BSD (for ZFS) for backup servers
My flickr
I am yet to try BSD... will download an ISO and tinker with it.. which flavor do you guys suggest, the ones with the most resources?
I would stick with FreeBSD if I was just getting into it. It has the biggest community, and excellent documentation:
http://www.freebsd.org/doc/en_US.ISO...ooks/handbook/
My flickr
Seeing you guys are talking about BSD & ZFS see,
http://bsdmag.org/magazine/1809-tuning-zfs-on-freebsd
Tuning ZFS on FreeBSD
ZFS is a modern 128-bit file system based on the copy-on-write model. It originates from the OpenSolaris project and has first appeared in FreeBSD in 2008. ZFS has many innovative features including an integrated volume manager with mirroring and RAID capabilities, data checksumming and compression, writable snapshots that can be transferred between systems and many more. In this article the author is going to discuss several tuning options including sysctl(2) knobs and give examples how can ZFS performance and efficiency can be measured and evaluated. This article is intended for FreeBSD users with ZFS version 28 available since 8.3-RELEASE and 9.0-RELEASE.
entia non sunt multiplicanda praeter necessitatem
This shows you haven't had any real world experience with production environments.
There is penalties payable if you cause down time to the big boys systems. Think R50k per 10mins at the lighter end of the scale. This will get you fired I have seen it happen more than once. So I think its actually the other way round that you need to take time and learn what is actually going on in the field.
While that is true in principle, it's also BS 99% of the time. I see this every day at work (I work for a hosting co that hosts these "big boys" but also the small boys and everything in-between): Client has downtime for whatever reason, and scream at us that they're losing tens of thousands of dollars per hour or millions a day. But they're hosting their entire business on a single server.
The companies who are serious about keeping their stuff running, choose the right hardware to facilitate this, and build their applications to cope with the loss of a node or multiple nodes, and some actively break stuff in their production environments - Netflix is famous for this.
My flickr
Bookmarks