Maybe this is what you need?
http://www.naken.cc/mikehup.php
I use this on a CMS site, where the users upload imagefiles with ftp. After
that, they use a php webinterface to start an importscript (written in
Perl). By doing this command in php:
system("/usr/local/bin/mikehup /usr/bin/perl
/www/servers/netlag/cronscripts/import_billede.pl &");
The importscript is started and executes in the background while the
php-script finishes execution.
Hope that helps
- Carsten
> -----Oprindelig meddelelse-----
> Fra: Joseph Tate [mailto:jtate@;mi-corporation.com]
> Sendt: 15. oktober 2002 21:15
> Til: Zeev Suraski
> Cc: Andrei Zmievski; PHP Developers; Jason Priebe
> Emne: Re: [PHP-DEV] [4.3] Current critical bugs
>
>
> Throw me a bone then. What is the suggested way to offer php developers
> the opportunity to run code after the connection has been closed? Even
> if it only works under Apache on Linux? Also if the 4.1.0 behavior is
> the "correct" behavior, why is the function still documented as the
> 4.0.x behavior?
>
> I'll admit that the company I work for is probably the only one using
> this function, but we depend on it. We do heavy image processing work,
> using image magick, called from clients using wireless networks, where
> it hurts us to keep connections open for long periods of time. If we
> can't fork some processing to the background, our users think our app is
> slow, and we lose sales. It's that simple. "Correct" behavior or not,
> we need the functionality.
>
> My patch, I hope, will be ready by the end of the week. Adding a
> parameter to the register_shutdown_function will not be possible, since
> the function was changed a while back to allow users to specify
> arguments to the function being registered. Instead a second function
> will be created: register_offline_function offering the 4.0.x behavior.
>
> Joseph
>
> Zeev Suraski wrote:
> >> Summary: Under Apache, register_shutdown_function() broke between 4.0.x
> >> to 4.1.x
> >> URL: http://bugs.php.net/bug.php?id=15209
> >
> >
> > I stated my stand on this, I believe that the 4.1.0 behavior is
> the more
> > correct one.
> >
> > I have to go now, but I'll look at the rest of relevant bugs
> later today.
> >
>
>
> --
> PHP Development Mailing List <http://www.php.net/>
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
