What are the paths on your servers to programs commonly called from scripts?
Perl – /usr/bin/perl
Python - /usr/bin/python
Bourne Shell - /bin/bash
TCL - /usr/bin/tcl
Sendmail - /usr/sbin/sendmail
Do you place any limits on the use of CGI scripting?
The only limits we impose are resource related. Our standard account configuration allows scripts a maximum of 10 seconds of processor time, 8 Megabytes of memory, and a limit of 4 child processes per script run. These limits were introduced to prevent customer scripts from occupying huge amounts of memory or tying up processors for long periods of time, which affects performance for other customers. The child process limit also protects against a fork() bomb, which can quickly use up all available system resources. We also make use of a suexec wrapper, so that scripts are executed under your account, rather than that of the web server. We believe that most users will not find this a limitation, however if your script does legitimately require more resources, the limit can be increased (but not removed) without charge. Please contact email@example.com for details of this.
Users are provided with direct upload access into their own private CGI directory, we do not have a policy of vetting CGI scripts. We do not place any restriction on the use of data or configuration files within the CGI area, these files can also be written to by scripts if you wish. We do not restrict access to standard server environment variables, or place any restrictions on the use of particular system calls in your scripts.
Our policy on scripting is designed to aid our customers in rapid development of bespoke server-side applications. Please respect that our web servers are a production environment, if you feel your script requires testing in a development environment prior to being run on a production web server, please contact firstname.lastname@example.org.