Issue the command "perl " from the command line, where "scriptname" is the relative or absolute path to the Perl script. If problems with the execution of the script are encountered, they will be reported on the terminal by the Perl Debugger.

Applications using a UNIX-style build process will typically require a shell environment and set of POSIX tools, for executing configure scripts and building the application. The Cygwin environment was once the only choice available to fill this role, although recently the MSYS environment was released to offer MinGW developers a more lightweight alternative. The use of both these environments with MinGW is described in more detail below.

Start your script as you would any perl script (e.g. #!/usr/bin/perl, #!/usr/local/bin/perl, #!/opt/bin/perl, [built static? then #!/usr/bin/tkperl], whatever, see the perlrun(1) man page for more information).

brings a new and exciting answer to this question: PAR, a "Cross-Platform Packaging and Deployment tool", originally developed by Autrijus Tang. Before PAR, the only public support for Perl/Tk "compilation" was in the Dr.

Yes. Simply use the "Execute" script command within your script, as in the following example: Secondly, when in receipt of TLV-structured data from the SIM, SIMcommander provides script commands to break this data down into smaller parts, and also to search for particular TLV tags.

A good starting place is the printed documentation that came with Windows NT and on the Windows NT CD in the support\books directory. Windows Help files are also available. You can get some in-depth information on Windows NT from the Windows NT Resource Kit, available at bookstores and from Microsoft. Microsoft TechNet is also a valuable resource. Printed documentation comes with Windows 95, as well as some documentation on the CD-ROM. Help files are available from the Start menu.

For societies, rather than running CGI/PHP scripts as an individual, we have introduced a unix user for each society. This user cannot log in, however it is used as the user under which all society PHP/CGI scripts are run. Outgoing email generated by society CGI/PHP scripts will, by default, appear to come from [socname]-webmaster@srcf.ucam.org. See Society email addresses. Note that any CGI/PHP script which hogs the CPU for more than 2 minutes will be terminated by the system.

In this section we have grouped together a series of fequently asked questions regarding web sites on the OUCS web server. If you cannot find the answer to your question here, please send your question to us via the Help Pages and Form.

Yes. Once you have completed the installation of bbBoard v2, bring up a command line (SSH/Telnet is fine) to bbv2's base directory, and type:

We haven't provided Perl scripting for our users, primarily because of security concerns. It's easier to break stuff with Perl scripts. However if you would like to use some Perl scripts, or write your own, let us know and we'll see what we can arrange.

For more information on Perl scripts we suggest the following books and have set up direct links to them at amazon.com

We don't recommend or support it and we have not tested it. As these scripts run for extended periods of time it is likely that they will timeout if run through a web browser. They should be run from the shell

Perl scripts can be run from anywhere on your domain inside the Windows 2003 /wwwroot directory. They do not have to reside inside the cgi-bin directory. If we were a Unix hosting company (which we aren't) we would have to set permissions, but running Windows 2003 servers with our configuration, it doesn't make a difference where you put them.

Yes. We provide our Web Hosting customers with a CGI-BIN in their Web directory. • Path to Perl: /usr/bin/perl • Path to Sendmail: /usr/sbin/sendmail

If you have checked all of the above and are still experiencing difficulties. Please contact us again.

You are welcome to use any script that you want. However some scripts use way too much of the CPU. If this is the case we will contact you and request that you make changes so that we can maintain a fast server for everyone. Please note that any support for your own scripts should either be directed to the author of the script or the appropriate newsgroup.

Perl scripts are uploaded in the same way as any other file you have on your web site: by using ftp software such as ws_ftp or cute ftp for pc or fetch or anarchie for mac. However, once the files have been uploaded you will need to set them so that they are executable (see next section). Make sure to upload the files in ascii mode. If you do not do this, the file will be uploaded in ms dos format and every line will end with ^M (the dos end of line character).

Everytime a CGI coded in Perl is executed on your website, the server has to launch the Perl interpreter, the Perl interpreter will then analyze the script's syntax, it will then compile the script and then execute it. Although all of this happens in less than a second, it puts too much load on a server, specially if the script is being excuted repeatedly. A solution for this is using a method that will allow the compiled script to remain in memory, waiting to be executed.

If /opt/hpapache2/logs/error_log says "Apache.pm" failed to load then mod_perl has not loaded and all perl scripts will fail. This is usually due to perl binaries not being in the PATH or the PERL5LIB environment variable not being set to include following as a single line: SOLUTION: Verify that perl is installed in /opt/perl/bin and that /opt/perl/bin/perl and /opt/perl/lib/5.6.1 exist.

Because mod_perl runs within an httpd child process, it runs with the user-id and group-id specified in the httpd.conf file. This user/group should have the lowest possible privileges. It should only have access to world readable files. Even so, careless scripts can give away information. You would not want your /etc/passwd file to be readable over the net, for instance. Different mod_perl scripts run successively using the same Perl interpreter instance.

Perl scripts can be placed in either of two directories, cgi-bin or mod_perl. For performance reasons, it is suggested that you use the mod_perl directory since scripts in this directory will be run under Apache's mod_perl extension. Most, but not all, Perl scripts will run under mod_perl, so you may need to use cgi-bin. Both the mod_perl and cgi-bin directories are located under the default installation directory folder (e.g.