Greetings, Martino Dell'Ambrogio.
In reply to Your message dated Tuesday, November 4, 2008, 15:11:45,
> - if I use wget --spider (HEAD request) the script exits just after the
> first output, all the functions below never get executed
It is intended behaviour.
Apache sending headers at the moment
On Tue, 04 Nov 2008 13:24:41 +0100, Jochem Maas wrote:
> try testing for the request type (i.e. HEAD) and if found don't output
> anything at all.
This is a nice workaround and works perfectly, thanks!
> seems like apache (not the user) is shutting down the request as soon as
> it recieves the f
> - if I use wget --spider (HEAD request) the script exits just after the
> first output, all the functions below never get executed
>
> This has nothing to do with any system command.
Then have your HTTP request trigger a system command that runs on
regardless. The HTTP request continues on after
Martino Dell'Ambrogio schreef:
> On Tue, 04 Nov 2008 11:59:20 +, Richard Heyes wrote:
>
>>> I need the PHP script to keep running until the end)
>> Until the end of what? Time?
> Until the end of the script.
>
>> If you want your HTTP request to finish and
>> a script to continue regardless t
On Tue, 04 Nov 2008 11:59:20 +, Richard Heyes wrote:
>> I need the PHP script to keep running until the end)
>
> Until the end of what? Time?
Until the end of the script.
> If you want your HTTP request to finish and
> a script to continue regardless then use the method I suggested, an
> sta
> I need the PHP script to keep running until the end)
Until the end of what? Time? If you want your HTTP request to finish
and a script to continue regardless then use the method I suggested,
an start a shell process going.
--
Richard Heyes
HTML5 Graphing for FF, Chrome, Opera and Safari:
http
> The question here is: why a PHP script called via 'wget --spider' through
> Apache/2 gets killed as soon as the HTTP reply code is sent, even if
> ignore_user_abort() is set?
A script ending naturally is not the same as a user aborting.
--
Richard Heyes
HTML5 Graphing for FF, Chrome, Opera an
On Tue, 04 Nov 2008 11:37:15 +, Richard Heyes wrote:
>> The question here is: why a PHP script called via 'wget --spider'
>> through Apache/2 gets killed as soon as the HTTP reply code is sent,
>> even if ignore_user_abort() is set?
>
> A script ending naturally is not the same as a user abor
On Tue, 04 Nov 2008 10:03:11 +, Richard Heyes wrote:
>> I am trying to get a script to run in background no matter what, but I
>> am obviously doing it wrong.
>
> 1. Have it executed via a shell command. 2. Redirect all output.
> 3. Append the ampersand.
This is not what I need, but thanks.
> I am trying to get a script to run in background no matter what, but I am
> obviously doing it wrong.
1. Have it executed via a shell command.
2. Redirect all output.
3. Append the ampersand.
eg. A commandx such as:
sleep 5 >/dev/null 2>&1 &
would become:
/dev/null 2>&1 &');
?>
--
Richar
Hi there,
I am trying to get a script to run in background no matter what, but I am
obviously doing it wrong.
Here is the entire code:
The file /tmp/aborting get touched if I abort the connection in a
browser, or if I run "wget blabla/script.php" and kill wget... in fact it
works perfectly
11 matches
Mail list logo
