On Wed, 2003-02-26 at 09:37, Anne Wilson wrote:
> On Wednesday 26 Feb 2003 4:40 pm, civileme wrote:
> 
> > If you want stable as in server use there
> > is Corporate Server, and MNF.  
> 
> Fair comment.
> 
> In the meantime, there is the problem of getting the exposure in the press 
> that others get.  Over and over I see in Linux Format that Mandrake is 
> brilliant for desktop use, but when they want to explain something they use 
> Suse.  Why?
> 
> More to the point, what can *we* the users do to help the situation?
> 
> Anne

I suppose purchase and use Corporate Server. I use Mandrake on my own
servers, but that's okay because they generally double as desktops :-)
The extra horsepower that others use for eye-candy, I use for nearly
1300 emails and 600 dynamically generated pageviews a day.

However, I have to agree that the regular Mandrake product is not a
suitable server for corporate environments, as most admins don't know
how to use its tools (especially msec) and those tools will bite badly.
I'm highly embarassed by the fact that I built a MDK9.0 Nagios box as a
backup to a RH 7.3 Nagios box, and the MDK one has been disk wiped and
replaced with RH. Why? Because two weeks after I left msec saw fit to
disable all logins because of password aging, and in trying to fix this
from the console the admin either uncovered or introduced a PAM problem
that caused the passwd program to segfault. I had documented and backed
up the Nagios work, so it was only two hours work to replace Mandrake
with RH, but the lasting impression at that company is that Mandrake is
a cute desktop which is unfit for server work.

msec had been set to level 4 during install, then reset to level 3
because level 4 is too restrictive to allow Nagios to work (the nagios
user process is prevented from looking in /proc). The reset wasn't
complete, so the level 4 password aging policy was still in effect.

-- 
Jack Coates
Monkeynoodle: A Scientific Venture...


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to