I've been following this just at a high level, so if I'm posting a method
that you've already tried and dismissed please forgive me.
You can try forking followed by separating from the parent session. I
think that will help keep your program from getting killed when apache is
restarted or stopped.
Cameron,
Have you tried issuing the command to `at`? If you don't need to
interact wih the report generator, and can pass all the parameters in
the command line or via a tmp file, this is a great solution.
at (and the corresponding atd) will preserve your environment vars and
other niceties.
Cameron B. Prince wrote:
I have a report generator program written in Perl that I need to start from
a CGI. The program takes about 15 minutes to run, so I must fork or double
fork. I have two goals:
1) Have no zombies when the program completes
2) Fork in such a way that restarting Apache doesn't
Hi,
I guess this is off topic for this list, since I would be doing this no
matter if I was running CGI or mod_perl or whatever. I am pretty desparate
to get this working, and if anyone wants to earn some cash helping me fix
things PLEASE call me at 250 655-9513.
I have been trying to accomplish
Eric Frazier wrote:
...
> But then I found I was using 5.8.. Thanks to a guy on comp.lang.perl.misc I
> know that there is a change in how signals are handled, they call it
> deferred signal handling because Perl now is suppose to wait until the
> Interpeter is in a safe state. As I understand it t
mes reasonably stable. If anybody has a better way, then I'm all ears.
Cheers!
-Original Message-
From: Eric Frazier [mailto:[EMAIL PROTECTED]
Sent: 16 September 2003 12:24
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: mod_perl v2 Forking
Hi,
I guess this is off to
Hi,
That sound like one way to go, I want to be very careful with something like
this. You speak as if restoring 5.6 behaviour is the best or only way to go.
Do you see any other alternatives?
Thanks,
Eric
At 04:57 PM 9/16/03 +0200, Rafael Garcia-Suarez wrote:
>Eric Frazier wrote:
>...
>> But
when it's done, kill the child:
> exit(0);
> }
>}
>
>This seemes reasonably stable. If anybody has a better way, then I'm all ears.
>
>Cheers!
>
>-Original Message-
>From: Eric Frazier [mailto:[EMAIL PROTECTED]
>Sent: 16 September 2003 12:24
-
From: Eric Frazier [mailto:[EMAIL PROTECTED]
Sent: 16 September 2003 12:57
To: Stephen Hardisty
Cc: [EMAIL PROTECTED]
Subject: RE: mod_perl v2 Forking
Hi,
Doing this "works" for me. But I am ending up with some errors that I didn't
have before. Of course my bosses would get mad if I
er way, then I'm all ears.
>
>Cheers!
>
>-Original Message-
>From: Eric Frazier [mailto:[EMAIL PROTECTED]
>Sent: 16 September 2003 12:24
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Re: mod_perl v2 Forking
>
>
>Hi,
>
>I guess this is off
and fluffy to close it before the exit.
>Otherwise, I don't know I'm afraid.
>
>-Original Message-
>From: Eric Frazier [mailto:[EMAIL PROTECTED]
>Sent: 16 September 2003 12:57
>To: Stephen Hardisty
>Cc: [EMAIL PROTECTED]
>Subject: RE: mod_perl v2 Forking
>
&
Haven't read much of this thread, but is POE an option ?
> -Original Message-
> From: Eric Frazier [mailto:[EMAIL PROTECTED]
> Sent: 16 September 2003 13:17
> To: Stephen Hardisty
> Cc: [EMAIL PROTECTED]
> Subject: RE: mod_perl v2 Forking
>
>
> :)
I guess you could, but if there's already a load of code mightn't be a bit of a pain
POE-ing it?
-Original Message-
From: Gareth Kirwan [mailto:[EMAIL PROTECTED]
Sent: 16 September 2003 16:50
To: 'Eric Frazier'; Stephen Hardisty
Cc: [EMAIL PROTECTED]
Subject: RE:
whoah! people, please trim the irrelevant stuff in your replies, this thread
keeps on growing for no reason. Perhaps you should read
http://perl.apache.org/maillist/email-etiquette.html#Extracts_From_Other_Posts
if you are new to this list. We want these threads to be useful for those who
will la
14 matches
Mail list logo