|
2.1) Access logs
"I can't find my access log!"
They are in /www/logs/. So, the access log for userid.com is in
/www/logs/userid-access-log.
2.2) Cgi-bin scripts
"Where do I put my cgi-bin scripts?"
Put them in the subdirectory cgi-bin which should be under your www
directory.
"I don't have a cgi-bin directory!"
Make it by typing mkdir cgi-bin while in your www directory.
"How do I access cgi-bin scripts in the cgi-bin directory?"
If your domain name is "lastminute.com", access them as
http://www.lastminute.com/cgi-lastminute/script_name.
"Hey! /cgi-lastminute/ doesn't work for me!"
Ask us to activate your cgi-bin directory.
2.3) Perl scripts
"I am being told file not found"
Upload your Perl script in ascii mode, not binary mode.
Use rz -a for telnet users, or the ascii mode for ftp users.
Sometimes it seems like this is asked about once a day, so we're going to
repeat it, loudly.
Upload your Perl script in ascii mode, not binary mode. Use rz -a for
telnet users, or the ascii mode for ftp users.
We have Perl4 and Perl5 on the server. You can find them by typing "whereis perl" at the shell prompt, but the standard path of your script should work. Normally, it is /usr/bin/perl
If you NEED perl4, you could change the first line of your script to
#!/usr/bin/perl4
2.4) Imagemaps
"Hey! my imagemaps don't work!"
This is a proper imagemap reference:
<a href="djonly.map"><img src="djonly.gif" ISMAP> </A>
Possible mistakes:
You didn't use NCSA format.
Our server is NCSA format and not CERN !
Instead of saying djonly.map, you included your domain name or other
information in your reference. (Sometimes causes problems.)
You forgot to use the extension .map.
You forgot the word ISMAP.
You forgot to include the default line as the first line in your imagemap.
When specifying rectangles, you didn't include the small numbers first, as in
0,0 100,100.
2.5) Anonymous ftp
"Where should I store files for anonymous ftp access?"
Put files in the directory named anonftp in your home directory. This will
allow a file to be accessed by a customer with
ftp://domainName.com/pub/domainName/file.
2.6) Setting permissions for files and directories
"Hey, how do I stop people who are not in my group from reading a
directory?"
Type chmod o-r directory while you are in the directory above it.
"I don't care if people in my group can read my directory, but I don't want
them to write in it!"
Type chmod g-w directory while you are in the directory above it.
"Tell me more about permissions, they sound neat!"
To list the access permissions of a file or directory, type ls -ls *. (you will see
this also by typing "ls -al") r=read access, x=execute access, w=write access.
The first three letters apply to you, the second three letters apply to your
group, the last three letters apply to everyone else. Execute access enables
you to run programs or enter directories.
Examples of using chmod:
PEOPLE PERMISSIONS
u = the file's user (or owner) r = read access
g = the file's group x = execute access
o = others w = write access
a = the user, the group, and others.
chmod a+w = let everyone write to the file
chmod go-r = don't let people in the file's group or others to read
the file
chmod g+x = let people in the file's group execute the file
2.6) Server Side Includes
If you wish to use server side includes in a web page, the file name of that
web page must have the .shtml extension (eg. index.shtml)
We allow SSI`s on our server. The 'SS' stands for Server-side and the 'I' stands for whatever your consultant tells you. 'Includes' and 'interface' are both
popular. (SPML -- Server Parsed Markup Language -- is also used to refer to the code you write. Really, you can learn the entire small command set SSI
provides before you learn the acronyms.) Basically, SSI is a mechanism
whereby you can have our server do something to your HTML before sending it to the browser. SSI does some of the same things CGI does. Some
differences are that SSI doesn't handle forms (at least, I haven't seen anyone
bother trying) but CGI is much more involved if you just want another file or the output of a program included in your document. To have a document
parsed for SSI directives, give it the extension .shtml instead of .html. Formal documentation is available from within the Apache manual.
|
