Re: Calling a Command line tool from an application
Re: Calling a Command line tool from an application
- Subject: Re: Calling a Command line tool from an application
- From: Michael B Allen <email@hidden>
- Date: Wed, 13 Apr 2005 00:26:24 -0400
On Tue, 12 Apr 2005 16:40:20 -0600
Kevin Harris <email@hidden> wrote:
> In any case, the man pages for fork(2), pipe(2), close(2), dup2(2),
> exec(3), and wait(2) should all come in handy. For twiddling the
> close-on-exec behavior, the fcntl(2) man page (F_GETFD and F_SETFD) will
Actually I think it would be easier to use forkpty. That is also the only
way to ensure the program will behave as it would on the commandline. It's
also the only way to run something that requires interactive control.
Mike
--
IRC - where men are men, women are men, and the boys are FBI agents.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden