Perl scripts usually have a special first line that specifies the path to the Perl interpreter. The correct paths on our system are:Which Perl modules do you support?#!/usr/bin/perl4...for Perl 4, and:#!/usr/local/bin/perl...for Perl 5.For a list of the specific version numbers of perl we support refer here.
If you want to run Perl from the Telnet command line, perl4 will run 4, and perl5 will run 5.
Under FreeBSD, sendmail is not in /usr/lib. The correct path to sendmail is:Cron Jobs (Automated Job Processing)/usr/sbin/sendmailFor accounts that have been upgraded to qmail the correct path is:/var/qmail/bin/qmail-inject
or
/usr/sbin/sendmail will also still work
A cron entry looks similar to the following:
In this case, the script "script.pl" would be run nightly at 3:30 AM.
30 3 * * * /usr/bin/nice -20 /bin/rm /usr/home/username/temp/*The "30 3 * * *" requires a bit more explaining. The time a cron command is executed is controlled by the 5 numbers that precede the cron directive.to remove all files from some temporary directory you might have each night at 3:30 AM, as in the earlier example.
The first number is the minutes after the hour (0-59).A * in place of any of the values matches all possibilities (for instance, in the given example the script runs every day because the *'s for day of the month, day of the week, and month of the year match all values).
The second is the hour of the day (0-23, with 0 being 12 AM).
The third number is the day of the month (1-31).
The fourth is the month of the year (1-12).
The fifth is the day of the week (0-6, with 0=Sunday and 6=Saturday, etc).
Multiple values are separated by commas. For instance, you might start with 15 1,3,5 * * * to run a script every day at 1:15, 3:15, and 5:15. (Note that our policies prohibit a program running via cron more often than once every two hours.)
Once you have your cron directive file (say, cron.file) in your account, you must connect via telnet and issue the command:
crontab cron.fileusing the name you gave the file. (Note that you must be in the same directory as the cron file at the time.) After this, your cron should be activated. If the programs running via cron generate errors, the cron daemon will e-mail them to your account.
In your public_html subdirectory or any subdirectory thereof, you can create a file called .htaccess and place, among other things, AddType commands in it. The syntax for AddType is:
AddType application/octet-stream dat
AddType image/pnm pnm
These examples indicate that any file ending with dat is a plain binary file (to be downloaded, not viewed on-screen), and that any file ending with pnm is a special image type (which most browsers will not recognize for display purposes at this time, unfortunately).
Some cell phones and pagers now have the ability to read website documents on them. This technology is widely becoming a recognized standard as many websites create special content for such devices. To that end, WEBster Computing Services fully supports use of the Wireless Markup Language (WML) for Wireless Application Protocol (WAP).The WAP gateway retrieves WML pages from a webserver via normal HTTP. The only difference is, you have to configure your webservers to map the following extensions to the appropriate mime types as follows:
# MIME Types for WAP
AddType text/vnd.wap.wml .wml
AddType image/vnd.wap.wbmp .wbmp
AddType application/vnd.wap.wmlc .wmlc
AddType text/vnd.wap.wmlscript .wmls
AddType application/vnd.wap.wmlscriptc .wmlscYou should naturally also name your WML web files with these extensions to make this work. These mime types are currently scheduled for installation on our servers. If they are not already present on your server refer directly above to the MIME ADDITION section. Mime types such as these can be added at any time into your account by you.
For more information on WML and WAP please visit TheWirelessFaq