stem service as Jeremy Ardley suggests in a different reply. > > Exactly: > > script > /tmp/script.log 2>&1 & > > (adjust paths to taste). For good measure, and if your shell > has job control, it will output the job number and PID, like > so: > > [1] 15211 > > (1 is the job number, 15211 is the PID, actual numbers will > vary). You then issue > > disown %1 > > (assuming bash here), which lets your shell "forget" about job > number 1 and keep it for messing around once you leave your > shell (in some setups, terminating the shell might terminate > the background jobs, but my memory might be fuzzy). >
Thanks for all your helps. I know convert it to a perl script and run it under App::Daemon for background jobs. regards Tom -- sent from https://dkinbox.com/
