Quoth David Powell da...@drp.id.au,
Indeed System.Process does work for me. I had avoided it because it is a
little more awkward to use it when you want the actual PIDs. I don't
understand why System.Process.runProcess works for me, but executeFile does
not. I did find this issue (for
executeFile is failing for me on Mac OS X 10.5.8, with ghc 6.12.1 when
compiling with -threaded. Compiling without -threaded, or running on
linux is fine.
When compiled with -threaded, the following snippet produces the error:
testProg: /bin/echo: executeFile: failed (Operation not supported)
Hello David,
Sunday, May 16, 2010, 7:18:29 PM, you wrote:
executeFile is failing for me on Mac OS X 10.5.8, with ghc 6.12.1
when compiling with -threaded. Compiling without -threaded, or running on
linux is fine.
forkProcess $ executeFile /bin/echo False [Ok] Nothing
afair, forkProcess
On Mon, May 17, 2010 at 1:33 AM, Bulat Ziganshin
bulat.zigans...@gmail.comwrote:
Hello David,
Sunday, May 16, 2010, 7:18:29 PM, you wrote:
executeFile is failing for me on Mac OS X 10.5.8, with ghc 6.12.1
when compiling with -threaded. Compiling without -threaded, or running
on linux is
Works fine on 10.6.3. If you run with +RTS -N2, though, you'll get
forking not supported with +RTS -Nn greater than 1
The reason for this is that forking won't copy over the threads which
means that the Haskell IO manager stops working (you'd have to somehow
reinitialise the RTS while leaving
Indeed System.Process does work for me. I had avoided it because it is a
little more awkward to use it when you want the actual PIDs. I don't
understand why System.Process.runProcess works for me, but executeFile does
not. I did find this issue (for python)
http://bugs.python.org/issue6800which
