Reply to thread

Message: [QUOTE="Darren Dunham, post: 4745792"] What leads you to think that it "acts like it is tainted"? What error messages are you getting? No. Because this avoids the shell (the purpose), you can't tell the shell to run it in the background. More and more I begin to suspect that this isn't the result of tainting at all... However, if you want to "detach" it, either run it in a shell explicitly.. ("/usr/bin/sh","-c","/usr/src/client/client",$p1,$p2,$p3,$p4,&) or fork/exec yourself. unless (fork) # no error checking here.. { # this is the child exec("/usr/src/client/client",$p1,$p2,$p3,$p4); } # only parent reaches here... That exit line is never executed. The perdoc on exec will tell you why. If you want to do that, use a fork as above. Why do you think it's tainted? [/QUOTE]