Most of the problems that I hear from folks with RAQs are the ones that
constantly meddle via telnet and then expect support for their screwups.
I strongly recommend sticking to the web interface. Cobalt built a really
nice click and drool web interface to manage the server with. It does it
basic job extrememly well as long as you leave it alone.
We have quite a few RAQs, use them for what they are meant for, serving up
simple websites. It has given us the ability to add very simple sites on
the fly while still on the phone with the customer. That is impressive and
what the Cobalt Product line is meant for.
If you are wanting to roll your own solution, then buy one of the many 1RU
servers on the market, then go to it, but don't expect a RAQ to solve all
of your enterprise problems, it was never meant to do that.
Have a nice day :)
Flame suit on...
On Tue, 4 Jan 2000, J. Masterson wrote:
> We just got a Raq3i, and I've been assigned to essentially administer
> the server. It'll be a web server for a single large site.
>
> Are many people forgoing the web interface in favor of using telnet and
> unix tools? I'm more comfortable with editing the httpd.conf myself,
> etc....
>
>
> --
> John Masterson
> Web Developer
> WAM!NET Missoula
> masterson@xxxxxxxxxxxx
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>
Rik Thomas rikt@xxxxxxxxxxxx
http://www.delaware.net
(p) 302.736.5515
_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-users