Hi,
That would be a good solution, but I need the stderr of the command to handle it. My app is a network troubleshooting app, and it uses commands to attempt to access websites. If a (network) error is thrown by a command, my app needs that error immediately to handle it. If I use background commands, I will not be able to tell if a command failed or succeeded. I also can't access /dev/null, as my app is sandboxed. My app has it's own "trash bin" called "Tests.log" that is never referenced. Could I use that? (But the main question is about the stderr).