When spawning an external command, as a programmer, you would definitely want to determine if you have succeeded in doing so.
Unfortunately,
posix_spawn (and
posix_spawnp) does not provide such a feature. To be accurate, there is no guaranteed way to synchronously determine if the function has succeeded in spawning the command synchronously.
In case of Linux, the function returns zero (i.e. success) even if the external command does not exist.
The document suggests that if the function succeeded in spawning the command should be determined asynchronously by checking the exit status of
waitpid. But such approach (that waits for the termination of the sub-process) cannot be used if your intension is to spawn a external command that is going to run continuously.
Recently I have faced the issue while working on
H2O, and have come up with a solution; a function that spawns an external command that synchronously returns an error if it failed to do so.
What follows is the core logic I implemented. It is fairly simple; it uses the traditional approach of spawning an external command:
fork and
execvp. And at the same time uses a
pipe with
FD_CLOEXEC flag set to detect the success of
execvp (the pipe gets closed), which is also used for returning
errno in case the syscall fails.
pid_t safe_spawnp(const char *cmd, char **argv)
{
int pipefds[2] = {-1, -1}, errnum;
pid_t pid;
ssize_t rret;
/* create pipe, used for sending error codes */
if (pipe2(pipefds, O_CLOEXEC) != 0)
goto Error;
/* fork */
if ((pid = fork()) == -1)
goto Error;
if (pid == 0) {
/* in child process */
execvp(cmd, argv);
errnum = errno;
write(pipefds[1], &errnum, sizeof(errnum));
_exit(127);
}
/* parent process */
close(pipefds[1]);
pipefds[1] = -1;
errnum = 0;
while ((rret = read(pipefds[0], &errnum, sizeof(errnum))) == -1
&& errno == EINTR)
;
if (rret != 0) {
/* spawn failed */
while (waitpid(pid, NULL, 0) != pid)
;
pid = -1;
errno = errnum;
goto Error;
}
/* spawn succeeded */
close(pipefds[0]);
return pid;
Error:
errnum = errno;
if (pipefds[0] != -1)
close(pipefds[0]);
if (pipefds[1] != -1)
close(pipefds[1]);
errno = errnum;
return -1;
}
The actual implementation used in H2O does more; it has a feature to remap the file descriptors so that the caller can communicate with the spawned command via pipes. You can find the implementation
here.
I am not sure if this kind of workaround is also needed for other languages, but I am afraid it might be the case.
Anyways I wrote this blogpost as a memo for myself and hopefully others. Happy hacking!
![はてなブックマーク - [メモ] OS XのホストからVMにnfsでファイル共有](http://b.hatena.ne.jp/entry/image/http://blog.kazuhooku.com/2015/10/os-xvmnfs.html "はてなブックマーク - [メモ] OS XのホストからVMにnfsでファイル共有")
![はてなブックマーク - [memo] Installing nghttp2 onto OSX](http://b.hatena.ne.jp/entry/image/http://blog.kazuhooku.com/2014/11/memo-installing-nghttp2-onto-osx.html "はてなブックマーク - [memo] Installing nghttp2 onto OSX")
![はてなブックマーク - [メモ] root権限でrsyncする方法](http://b.hatena.ne.jp/entry/image/http://blog.kazuhooku.com/2014/10/rootrsync.html "はてなブックマーク - [メモ] root権限でrsyncする方法")
![はてなブックマーク - [メモ] Apache+mod_sslでSIGBUSが発生した件](http://b.hatena.ne.jp/entry/image/http://blog.kazuhooku.com/2014/05/apachemodsslsigbus.html "はてなブックマーク - [メモ] Apache+mod_sslでSIGBUSが発生した件")
![はてなブックマーク - [perl][memo] File::Tempのバッドノウハウ](http://b.hatena.ne.jp/entry/image/http://blog.kazuhooku.com/2014/04/perlmemo-filetemp-tempfile.html "はてなブックマーク - [perl][memo] File::Tempのバッドノウハウ")