thanks for the info about your provider. Do you have any suggestions on how I can fix the code I have? How I can stop it from looping? should I only check for one signal, such as the term signal?

#!/usr/bin/perl -w -t

#load support for strict variables
use strict;

#load support for sockets
use IO::Socket;

#load posix support for trapping signals
use POSIX();

#load posix support for named pipes
use POSIX qw(mkfifo);

#start of creating a cross-platform method of determining
#the current script path and name
use FindBin();
use File::Basename();
use File::Spec::Functions;
my $script = File::Basename::basename($0);
my $SELF = catfile $FindBin::Bin, $script;
#end of creating a cross-platform method of determining
#the current script path and name

#create a new signal set
my $sigset = POSIX::SigSet->new();
#create the action you want performed on terminate signals
my $termAction = POSIX::SigAction->new('sigTERM_handler',
$sigset,
&POSIX::SA_NODEFER);
#attach the signal to the action you want performed on terminate signa
+ls
POSIX::sigaction(&POSIX::SIGTERM, $termAction);
.
.
.
#the above would be done for the int, pipe, and hup signals.

#start of the sub to run when the terminate signal arrives
sub sigTERM_handler {
#store the signal sent by the system
my $HTPad_signalCaught = shift;

#run the handler for all exit signals
&HTPad_exitSignalHandler("Terminate", $HTPad_signalCaught);
} #end of the sub to run when the terminate signal arrives

#start of the handler for all exit signals
sub HTPad_exitSignalHandler {
#reinstate the passed variables
my $HTPad_exitType = shift;
my $HTPad_signalCaught = shift;

#this daemon handler would also process the int, pipe, and hup signals
+.

unless (exec($SELF, @ARGV))
{ Die "Could not restart the script after a $HTPad_signalCaught signal
+ was received: $!"; }
} #end of the handler for all exit signals

#ignore child signals in order to do automatic child reaping
$SIG{CHLD} = 'IGNORE';

#enter the web server
&HTPad_webSserver();

#start of the web server
sub HTPad_webSserver {
.
.
.
open a socket
.
.
.
#start of the parent server accepting clients
while ($HTPad_client = $HTPad_server->accept()) {
.
.
.
parent fork() a write process for the client
.
.
.
process data from the client
.
.
.
#close the write child connection
close($HTPad_client);
#exit the write child to keep it from accepting new clients
exit(1); #should this be 1 or something else?

parent fork() a read process for the client
.
.
.
process data from the client
.
.
.
#send sig term to write child when client closes connection
kill ("TERM", $clientWritePID);
#close the read child connection
close($HTPad_client);
#exit the read child to keep it from accepting new clients
exit(1); #should this be 1 or something else?

} #end of the parent server accepting clients
} #end of the web server
[download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.