Cheers,
KM

It's not permissions, I've already set those correctly. I'm not using CGI.pm, I'll try that in a sec. It is printing out a correct header because it prints it out with the program's error messages when I run it from the command line.
I'll see about posting a test version somewhere in a bit.

I don't have access to the server log, I'm just a lowly webpage designer.

Ther server error that I get is:
Server Error This server has encountered an internal error which prevents it from fufilling your request. The most likely cause is a misconfiguration. Please ask the administrator to look for messages in the server's error log.

I've learned that this is the error the server returns for everything tho' so....

She-wolf
"Wha? I don't get it."

You should be able to see your errors in the server error log, and if you want errors to go to the browser, take a look at CGI::Carp. use CGI::Carp qw(fatalsToBrowser); will send error messages to the browser.

#!/usr/bin/perl -w

BEGIN
{#outputs al errors to $logfile
  my $logfile = "logfile.log";
  use CGI::Carp qw(carpout);
  open(LOG, ">$logfile") or die "Unable to write to $logfile: $!";
  carpout(*LOG);
}#
[download]

The above code error log will overwrite ( > ) the log each time your cgi is run. If you want to append just add another > (open ( LOG, ">>$logfile" ) ).

However you're still using sprite, and like athomason and merlyn suggested in your previoius post sprite is ancient and there's better solutions.

"cRaZy is co01, but sometimes cRaZy is cRaZy".
                                                      - crazyinsomniac

It took me two weeks to get our sys admin to install Sprite. That's one module. Getting DBI and the necessary stuff for that will take longer than my internship. Thanks for the code

She-wolf
"Wha? I don't get it."

Have you consisdered simply installing modules in your home directory - if you have one. At least it would be under your control and you'd have permissions to install there.

Then you need to make sure that you include something like
use /path/to/module/module::name;
or push the library path to the @INC variable
push (@INC,/path/to/module/module.pm);

in the top of your scripts.

MadraghRua

I put in the code you gave above and it taught me one thing. When I manually run the program from the command line, it gives me a log of the errors, but the errors it gives are irrelevant ones that don't effect the rest of the program(e.g. $webmaster is not referenced later in program).
But, when I try to access it through the form, it doesn't even activate the program, but it knows it's there. That brings me back to thinking it's permissions. But I've already tried various permissions, including the one listed in repsonse to my original post and the result is the same.
I don't get it.

She-wolf
"Wha? I don't get it."

Anytime text (via std or err output) is returned from a cgi it goes back to the browser.
If any text precedes(it usually does) the header ("Content-type: text/html\n\n" in the case of an html page) then the browser will think something is wrong. (It will think it is receiving a bad header.)

On the possibility of permissions problems. I have a few hosted sites that prevents any cgi from executing if the directory the script is in has potentially insecure permissions. (group/other read/write needed to be turned off, this might apply to the script too)
It may help, it's caught me several times.

She-wolf
"Wha? I don't get it."

First, you should use warnings (-w) and strict. Next, you should convert this to use CGI.pm, next add in CGI::Carp. This is very Perl4ish as it is and I would rather take the time to help debug it when it is, um, "updated" :) After making those changes, the problem itself may go away or become more apparant.

Cheers,
KM

She-wolf
"Wha? I don't get it."

You don't have permission to access /ergh.txt on this server.

Cheers,
KM

## Use the fabulous CGI.pm module is usually installed
use CGI;
my $C = CGI->new();

## create a code ref to the DIE event handler
$SIG{__DIE__} = \&my_die;

## create a sub to handle the dies

sub my_die {
    print $C->header,$C->start_html;
    print qq(<p>@_</p>);
    print $C->end_html;
}
[download]

and let it go.

When you use the CGI module you can also pass parameters to the script from the command line that you would pass from the form. i.e.:

$ ./my_script.cgi username=tenatious password=hideyho! age=1000 IQ=1
[download]

and lastly, make sure that the script is world executable:

chmod o+x my_script.cgi
[download]

That's almost exactly what

use CGI::Carp qw(fatalsToBrowser);
[download]

does. Nice shiny, reinvented, wheel. {grin}

-- Randal L. Schwartz, Perl hacker