RE: [PHP] system()

is there something with the PHP system command that makes it unable to spawn nohup background processes perl and PHP are closely related, so i cant really understand how an external perl program would be able to do things that PHP couldnt (at least in terms of this specific problem).... would a PHP call to "system('nohup ... &')" fail, or are your reasons for suggesting an external program based on something else other than simple feasability? ive never had to do anything like that before, and im not on a linux computer right now, so i cant test it myself. > -----Original Message----- > From: Christian Reiniger [mailto:creinig@mayn.de] > Subject: Re: [PHP] system() > > On Monday 19 February 2001 21:00, ..s.c.o.t.t.. wrote: > > i am not positive about this, but you could try making > > the amp process a background process by adding a > > " &" to the end of the command line > > (at least if you're using *nix) > > That alone won't help - "nohup" is also needed. > What he could do is write a small Perl/C wrapper for amp, which launches > the program in the background and returns its process id. Then he can do a > $AmpPID = system ("launchamp $Arg"); > > (the wrapper would have to execute "nohup amp $Args &") > > and add a 'stop' link > <a href="ampstop.php?pid=<?= $AmpPID ?>">Stop</a> > > And ampstop.php can do a > system ("kill -KILL $pid"); > > > > However, when they click Play, I want the same page to be > > > reloaded again, with nothing selected, and their (previous) selection > > > to start playing in the background. If they want to change their > > > selection, they can go ahead and pick other songs, and click Play > > > again - THIS is where the previous instance of the 'amp' program > > > should be killed, and a new one started, with the new play list > > > queued. And of course, it should also have a Stop button on the page > > > somewhere. >