Be aware: if you spawn a process from a cgi process, you will need to close stdin, stdout & possible stderr, in the child immediately it runs as they will usually inherit those from the parent, and the webserver waits for them to close before ending the session.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
In the absence of evidence, opinion is indistinguishable from prejudice.
Suck that fhit
| [reply] |
Execute another program but don't wait. might help. Regards, Karl
«The Crux of the Biscuit is the Apostrophe»
perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'Help
| [reply]
[d/l] |
| [reply] |
Modules like Parallel::ForkManager are very handy for this kind of needs-to-be-portable logic. If the two processes are intended to be children of the parent, the parent will have to wait for both of them to finish, because the children will be reaped when it does finish. Consider using the daemon/service facilities that are available (differently ...) in each environment, as an alternative to spawning them as children of an otherwise do-nothing parent., and especially if the children are intended to be long-lived. | [reply] |