【Linux + C语言】话说,你真的了解system接口的调用吗?
废话不多说,相信你肯定也在system接口上填过坑!先上一把它的正确操作:
#include <stdlib.h>
#include <sys/wait.h>
#define Debuging(fmt, arg...) printf(fmt, ##arg)
int new_system(char *cmd, char *resultout, int buflen, int *lenout)
{
int status = system(cmd);
Debuging("cmd=%s\n", cmd);
if (-1 == status)
{
Debuging("system error!\n");
}
else
{
Debuging("exit status value = [0x%x]\n", status);
if (WIFEXITED(status))
{
if (0 == WEXITSTATUS(status))
{
Debuging("run shell script successfully.\n");
return 0;
}
else
{
Debuging("run shell script fail, script exit code: %d\n", WEXITSTATUS(status));
}
}
else
{
Debuging("exit status = [%d]\n", WEXITSTATUS(status));
}
}
return -1;
}
示例代码中很好地展示了,如何判断system接口的返回值!
以下是linux man中关于system接口的介绍:
SYSTEM(3) Linux Programmer's Manual SYSTEM(3)
NAME
system - execute a shell command
SYNOPSIS
#include <stdlib.h>
int system(const char *command);
DESCRIPTION
The system() library function uses fork(2) to create a child process that executes the shell command specified in command using
execl(3) as follows:
execl("/bin/sh", "sh", "-c", command, (char *) 0);
system() returns after the command has been completed.
During execution of the command, SIGCHLD will be blocked, and SIGINT and SIGQUIT will be ignored, in the process that calls system()
(these signals will be handled according to their defaults inside the child process that executes command).
If command is NULL, then system() returns a status indicating whether a shell is available on the system
RETURN VALUE
The return value of system() is one of the following:
* If command is NULL, then a nonzero value if a shell is available, or 0 if no shell is available.
* If a child process could not be created, or its status could not be retrieved, the return value is -1.
* If a shell could not be executed in the child process, then the return value is as though the child shell terminated by calling
_exit(2) with the status 127.
* If all system calls succeed, then the return value is the termination status of the child shell used to execute command. (The
termination status of a shell is the termination status of the last command it executes.)
In the last two cases, the return value is a "wait status" that can be examined using the macros described in waitpid(2). (i.e.,
WIFEXITED() WEXITSTATUS() and so on).
system() does not affect the wait status of any other children.
ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7).
┌──────────┬───────────────┬─────────┐
│Interface │ Attribute │ Value │
├──────────┼───────────────┼─────────┤
│system() │ Thread safety │ MT-Safe │
└──────────┴───────────────┴─────────┘
CONFORMING TO
POSIX.1-2001, POSIX.1-2008, C89, C99.
NOTES
system() provides simplicity and convenience: it handles all of the details of calling fork(2), execl(3), and waitpid(2), as well as
the necessary manipulations of signals; in addition, the shell performs the usual substitutions and I/O redirections for command.
The main cost of system() is inefficiency: additional system calls are required to create the process that runs the shell and to
execute the shell.
If the _XOPEN_SOURCE feature test macro is defined (before including any header files), then the macros described in waitpid(2)
(WEXITSTATUS(), etc.) are made available when including <stdlib.h>.
As mentioned, system() ignores SIGINT and SIGQUIT. This may make programs that call it from a loop uninterruptible, unless they
take care themselves to check the exit status of the child. For example:
while (something) {
int ret = system("foo");
if (WIFSIGNALED(ret) &&
(WTERMSIG(ret) == SIGINT || WTERMSIG(ret) == SIGQUIT))
break;
}
Do not use system() from a program with set-user-ID or set-group-ID privileges, because strange values for some environment vari‐
ables might be used to subvert system integrity. Use the exec(3) family of functions instead, but not execlp(3) or execvp(3). sys‐
tem() will not, in fact, work properly from programs with set-user-ID or set-group-ID privileges on systems on which /bin/sh is bash
version 2, since bash 2 drops privileges on startup. (Debian uses a modified bash which does not do this when invoked as sh.)
In versions of glibc before 2.1.3, the check for the availability of /bin/sh was not actually performed if command was NULL; instead
it was always assumed to be available, and system() always returned 1 in this case. Since glibc 2.1.3, this check is performed
because, even though POSIX.1-2001 requires a conforming implementation to provide a shell, that shell may not be available or exe‐
cutable if the calling program has previously called chroot(2) (which is not specified by POSIX.1-2001).
It is possible for the shell command to terminate with a status of 127, which yields a system() return value that is indistinguish‐
able from the case where a shell could not be executed in the child process.
SEE ALSO
sh(1), sigaction(2), sigprocmask(2), fork(2), wait(2), exec(3), signal(7)
COLOPHON
This page is part of release 4.04 of the Linux man-pages project. A description of the project, information about reporting bugs,
and the latest version of this page, can be found at http://www.kernel.org/doc/man-pages/.
相关文章
- 在Linux上搭建C语言开发环境(linux搭建c开发环境)
- Linux查看接口状态:一个实例(linux查看接口状态)
- 操作excel展示Linux下Poi妙用:操作Excel(linux下poi)
- Linux之路:开启智能未来(linux征途)
- 学习Linux内核:如何使用它?(如何使用linux内核)
- 从零开始学习Linux下C语言编程(linux的c语言编程)
- Linux下安装C语言编译器(linux安装c编译器)
- 串在Linux中查找文件中的字符串(linux查找文件字符)
- 从U盘引导:制作Linux安装启动盘(u盘制作linux安装盘)
- 解压Linux解压TAR文件的简单步骤(linux.tar文件)
- 支付Linux下实现微信支付的简易教程(linux微信)
- Linux查看硬盘接口:终极解决方案(linux查看硬盘接口)
- Linux接口开发之路(linux接口开发)
- Linux发展史:追溯分支的来历(linux的分支)
- 深入理解:Linux 虚拟地址空间模型及应用(linux虚拟地址空间)
- 程序Linux下C语言程序的执行过程(linux执行c语言)
- 从C语言入门到Linux编程(c语言入门linux)
- 探索 Linux 用户的世界(查看linux用户)
- “快速复制:Linux实用复制快捷键大全”(linux复制快捷键)
- 深入剖析:探索Linux内核下的C语言编程技巧(linux内核的c语言)
- 「Linux开发必备」:C语言下的IDE工具汇总(linux下c开发ide)
- 编程Linux嵌入式C语言编程实践(linux 嵌入式c)
- Linux下使用C语言驱动串口设备(linux串口c语言)
- Linux系统:深入探索开放源码系统背后的神秘原理(简述linux系统原理)
- Linux开启图形化接口:颠覆传统的操作模式(linux 图形接口)