Troubleshooters.Com Presents

July 1999 Troubleshooting Professional Magazine: Troubleshooting CGI

Copyright (C) 1999 by Steve Litt. All rights reserved. Materials from guest authors copyrighted by them and licensed for perpetual use to Troubleshooting Professional Magazine. All rights reserved to the copyright holder, except for items specifically marked otherwise (certain free software source code, GNU/GPL, etc.). All material herein provided "As-Is". User assumes all risk and responsibility for any outcome.

<--CGI Troubleshooting On Someone Else's Server   |  Contents   |   Security Considerations-->

Due Diligence: Do It On Your Linux Box First

By Steve Litt
The sysadmin of Troubleshooters.Com's web host complemented me on developing and debugging my CGI on a Linux box before FTPing it to the live site. He said the majority of his CGI users just write the CGI, ftp it up there, and expect *him* to help them debug it. He clearly didn't have a lot of respect for people doing that. Neither do I.

It's very easy to make a Linux replica of your ISP (if your ISP uses Unix). The instructions are in the November 1998 issue of Troubleshooting Professional Magazine (URL in this issue's URL's section). Developing on the replica is 2-10 times faster than trying to develop even over telnet. On your private machine you can take diagnostic actions, like chmod'ing something 777, that you wouldn't dare do on your production or ISP server. You can reboot the machine. You can experiment in any way you choose. Only after understanding the nature of the problem do you need to consider a solution acceptable to your ISP.

All the same tools listed in this issue are equally valuable when troubleshooting on your own Linux ISP replica.

Steve Litt is the author of the upcoming book "Rapid Learning: Secret Weapon of the Successful Technologist". He can be reached at Steve Litt's email address.