> [...] but if groff is to be spawned from another program it > becomes a problem, either you spawn a shell runing a script or > spawn groff and have to bother with piping output. You can not > just fire off groff and forget about it. What a miss :(
Can't you fork, set up the appropriate file descriptors in the child, and then exec groff?
