-- edit SOLVED... subject line out of chars.

Sorry, the subject line can't say enough. Out of space.
Oh yeah, hello everyone. Forgot me manners.

I'm looking to call one exec from another (both mine) and want to 'ret' a(n) (possibly sizeable) amount of data. I'm also looking to Keep It Simple. Syscalls only, most likely, don't want to pull in too many deps.

One of my more promising ideas was to use one of my libs to expose a 'get/set/clear' function to handle the data transfer then tell the callee when to terminate. Kinda hack-ish, I know. Deps, yep, but they're my deps.

Still, I'm looking for a more convienient method. Lotsa good minds out there, surely someone's come across something like this before.
And I'm not gonna stop looking. Not a help vamp, fyi, i just gotta be missing something obvious.

Ears open, gimme a shout.
laters,
b

--edit small typo

I do similar parent/child interprocess communication using the socketpair syscall. When the parent forks you can remap stdin/stdout and crosswire them, or just use standalone socketpairs, etc. Between socketpair and dup2 you have some good options IMO. I suppose it all depends on how much control you have of your child program/exec environment as to how it needs to be put together.

$0.02 thusly

Interesting. Thanks, redsock that might be just what I'm after

I cannot mark this as solved. Perhaps a forum moderator could do so for me?

eilenbeb: I just removed the last part of the title "looking for options" and prepended "[solved]". If this is not to your liking you can always edit the title to something else.