Topic: Running CGI-Scripts on v4.1.1

[Ed]

I have a cgi-script that I want to run to proccess forms however to make it work I need to know the proper path to the cgi-bin to place in the form. The requirement within the cgi script is the path to the sendmail program but I understand that e-smith uses qmail. If someone could help me out by providing me with the correct path statements it would be much appreciated. Thanks again ...

[Andrew Roberts]

I'm running 4.1.2, and use the guestbook script from Matt's Script Archive.  I have the script set up to send mail when new entries are put in.

Go to a shell prompt and use 'which sendmail' and you should get a response as to where it lives.  On my system, it is in /usr/lib/sendmail .

In terms of a proper "path to the form," do you need the absolute path to the cgi, or the URL?  The absolute path to the cgi would be (assuming the site is in the primary):

/home/e-smith/files/primary/cgi-bin

The URL would be http://www.yourdomain.com/cgi-bin/yourscript.pl

Cheers,

Andrew

[Ed]

Thanks Andrew... no matter what I try I cannot get it to work I just keep getting "internal server errors". Is it that I have to go to version 4.1.2 of esmith? This is in my "primary" directory ... did you have your working with version 4.1.1? I have tried /usr/lib/sendmail ..  /usr/sbin/sendmail and /var/qmail/bin/sendmail all without success. The "POST" path in my form is as you suggested. If I was to send you my script could you check it for me? Thanks again

[dave]

hey, guys, isn't e-smith v.4 using qmail instead of sendmail?  i'm having the same prob getting a script to work, but here's how far i've gotten --

i can execute the script just fine from telnet or console by typing "perl form.cgi."  it mails out just fine.  but when i try to execute it via web i get "/cgi-bin/form.cgi not found" or "no permission" errors, even when i chmod 777 everything... weird.

i did have to reconfig the script to direct to /bin/mail (not (usr/bin/sendmail or something like that) to get it to link to qmail, but just can't get the apache-to-script thing to work...

if you've found any resolution, i would love to hear about it.

cheers.