|
|
Please note that this form is only for web host company's representatives. Responses from others will not
be posted. Customers should submit new reviews or email the original reviewer instead.
You are responding to the following review:
Friendly People, No Results - Review by
David Cloutman submitted on May 21, 2002 |
Customer's web site: www.lampfire.com |
Length of time hosted by this company: 1 year - 3 years |
Date when last hosted by this company (as of May 21, 2002): Less than 3 months ago |
Plan used: Silver Unix |
Customer service rating: 4 out of 10 |
Technical quality rating: 4 out of 10 |
Cost rating: 2 out of 10 |
Overall rating: 5 out of 10 |
Verio is a great service for the average marketing puke. As long as you publish flat HTML files and use Verio's free CGI scripts, you'll be satisfied with the genrally good uptime, decent stats packages, and polite 24/7 tech support. This last item might even justify paying the extra cost of their services. However, if you're a geeky programmer like me, welcome to Hell.
Most Verio customers are hosting static sites, so if you ever call them with a serious sytems question regarding the environment, the first person you deal with probably won't know how to fix your problem. Usually the issue is escalated to an administrator, and then its a coin toss as to whether or not your issue is properly resolved.
The key problem I've had with Verio is inconsistency in their environment. I find that when I use PHP to write a file, it will not consistenly assign ownership to the file, and that sometimes files are created that cannot be deleted by PHP scripts, or via FTP. Verio's solution to this problem was to suggest that I purchase one of their $150 / month virtual server accounts so I could get ssh access, which they claim is a security threat in a shared enviroment. This is, of course, rubbish.
More recently, Verio updated PHP, but did such a sloppy job configuring it that the error messages stopped displaying. It took me two weeks and a terse message to Verio's management team to convince them that developers need those messages to do rapid PHP development. After that, my error messages came back - for a week. Then they disappeared again.
Another problem I encountered was with chron jobs. Two of my Verio hosted clients have chron jobs that should back up the database on a nightly basis. Starting a chron job requires a call to tech support, I have never gotten a chron job to run on Verio more than once. Also, chron jobs can only be run at certain times of the early morning, and may not properly accomodate west coast users.
I haven't made extensive use of Verio's Perl or Python capabilities, however I would say, based upon my use of PHP, that you shouldn't even think about doing any major server side development in a shared Verio environment. Their staff and their servers are not adequately prepared for this.
|
This page is not connected with the company. These reviews and ratings are only the opinion of
the poster, are no substitute for your own research, and should not be relied upon for any purpose.
|