Interpreters, Etc.
Vaxxine strives to ensure that its support for the CGIs you run is the best that it can be. We try to ensure that we have the newest versions of any compilers and interpreters that you might wish to use are installed and ready to go. 

Maintaining this support means that upgrades must be done to various software from time to time. Normally this change is seamless. However, there are times when changes to items such as the Perl interpreter may reveal bugs or anomolies in your CGIs that prevent them from functioning in the manner that they once did. 

Vaxxine has chosen to address this issue by "freezing" the current software that runs under the "default" names. That is, the version of Perl that is started by your CGIs via lines like the one below will remain the same no matter what newer versions may come out. 

#!/usr/local/bin/perl

In the case above Perl version 5.005.02 will always be started, no matter what version of Perl is current. This does mean that you will not automatically enjoy the benefits (such as better speed, bug fixes, or additional features) of newer versions but it also prevents problems for errant scripts. You can easily upgrade the version of Perl you're using by changing the interpreter line. 

Newer, and existing older, versions of Perl will be started in a form similar to the following: 

#!/usr/local/bin/perl5.001
#!/usr/local/bin/perl5.00404

When a new version of CGI-oriented software is installed and Vaxxine has had a reasonable amount of time to test it WWW developers will be informed of the new version via the WWW Development List and the updating of the list of Installed Software Versions. 

Vaxxine would like to this opportunity to remind users that rely heavily on CGIs that they are not limited to using the interpreters that Vaxxine provides. If you have designed a site for a client, for example, and want to ensure that a particular version of Perl is always available then you can always install it in your own directory and use it from there. This does require some knowledge of UNIX and software design, but is far from impossible. The need to do this is even less likely with this policy but it has always been true that: 

If you unsure about your CGI's ability to run under different Perl versions then there is no reason you cannot install your own copy of the Perl interpreter, modules, etc., in your own directory. You would then have total control over that copy of Perl and could upgrade (or not upgrade) at your leisure. 

Compilers
Please note that if you desire to develop CGIs in compiled languages such as C or C++ you must send an e-mail to admin@vaxxine.com and specifically request access to the compilers you require.

Installed Software Versions
This list contains the different versions of the most popular interpreters and CGI tools found on Vaxxine's main WWW server and is updated on an on-going basis. All software is installed using the default configuration. If this is does not meet your needs then please compile your own version of the software and run it from your private directory. Please note that compiler versions are not listed and access to them is only granted if a specific request is sent to admin@vaxxine.com detailing your needs. 

Perl Interpreters

#!/usr/local/bin/perl    Frozen at Perl 5.005.02

#!/usr/local/bin/perl5.001
#!/usr/local/bin/perl5.00401
#!/usr/local/bin/perl5.00404
#!/usr/local/bin/perl5.00502
#!/usr/local/bin/perl5.6.1

PHP Interpreters

Current version of PHP: 4.4.6 (view PHP info)

Other server paths for developers:

Sendmail: /usr/sbin/sendmail