- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- apache2.0.43 and perl
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2003 05:27 AM
03-11-2003 05:27 AM
I installed hpapache 2.0.43 on an HPUX 11.0 with
perl 5.6.1
I am calling within a HTML page a perl script like:
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2003 07:26 AM
03-11-2003 07:26 AM
SolutionSays to stop and wait until you get something from the user who is generally expected to be sitting at the console. It is not clear to me how an HTML page is supposed to communicate with the console. Have you redirected STDIN somehow?
There are two scripts on the following page which might come in handy for your application:
http://www.perl.com/CPAN/scripts/CGI/index.html
CGIscripter and cgi-reflect.
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2003 08:02 AM
03-11-2003 08:02 AM
Re: apache2.0.43 and perl
i downloaded the script "cgi-reflect-1.6.pl" and put it
in place of mine.
What i am getting, is the following error:
"Error reading STDIN - ALRM! at cgi-reflect.pl line 78"
It seems that i really have a problem reading the
STDIN - is it possible that i misconfigured something in Apache?
Actually i exclude perl6.5.1 to be the problem. I installed
the HP distribution of perl 5.6.1 and i have the same problem.
josef
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2003 09:05 AM
03-11-2003 09:05 AM
Re: apache2.0.43 and perl
That's the idiom how one usually sets up timers in Perl by defining a signal handler that catches a SIGALRM.
The SIGALRM is then deliberately raised in an eval {} block through alarm() if a specified period has passed.
It looks as if your CGI script expeted data to be read from the special file handle STDIN where nothing was supplied.
I also wonder why one should do this in a CGI script, because the script is executed by the webserver.
The usual way to supply user input to a CGI script is trhough a form which is sent by the webserver to the client's browser.
The user then would have to fill out this form and press a submit button.
Thereon the webserver executes the script/program that is referred to by the ACTION attribute of the FORM tag.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2003 09:05 AM
03-11-2003 09:05 AM
Re: apache2.0.43 and perl
That's the idiom how one usually sets up timers in Perl by defining a signal handler that catches a SIGALRM.
The SIGALRM is then deliberately raised in an eval {} block through alarm() if a specified period has passed.
It looks as if your CGI script expeted data to be read from the special file handle STDIN where nothing was supplied.
I also wonder why one should do this in a CGI script, because the script is executed on by the webserver.
The usual way to supply user input to a CGI script is trhough a form which is sent by the webserver to the client's browser.
The user then would have to fill out this form and press a submit button.
Thereon the webserver executes the script/program that is referred to by the ACTION attribute of the FORM tag.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2003 09:10 AM
03-11-2003 09:10 AM
Re: apache2.0.43 and perl
That's the idiom how one usually sets up timers in Perl by defining a signal han
dler that catches a SIGALRM.
The SIGALRM is then deliberately raised in an eval {} block through alarm() if a
specified period has passed.
It looks as if your CGI script expeted data to be read from the special file han
dle STDIN where nothing was supplied.
I also wonder why one should do this in a CGI script, because the script is exec
uted by the webserver.
The usual way to supply user input to a CGI script is trhough a form which is se
nt by the webserver to the client's browser.
The user then would have to fill out this form and press a submit button.
Thereon the webserver executes the script/program that is referred to by the ACT
ION attribute of the FORM tag.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2003 09:20 AM
03-11-2003 09:20 AM
Re: apache2.0.43 and perl
Finally i have rewritten my old script
$buffer =
to
read(STDIN, $buffer, $ENV{'CONTENT_LENGTH'});
and it worked fine with perl 5.6.1.
josef