Skip to main content

Use of Execlp Functions C program Explained

Below code listing illustrates usage of execl function series, and talks about how to redirect the output from these functions.
Here is trick to redirect the output from execlp command series
In other words implematiation of "ls -l >/var/test.log"
first open file using "open" system call

#include
#include
#include

int open(const char *pathname, int flags);

then duplicate this file pointer with stdio file pointers
stdio file pointer are 0 for stdin
1 for stdout and 2 for stderr

use of dup2

dup and dup2 create a copy of the file descriptor oldfd.
int dup2(int oldfd, int newfd);


here is c example implementation in function;

int spawn(char* cmd)
{
pid_t child_pid;
int fptr,fptr2;
char tmp_devfs[20];
int child_status=-1,ret=-1;

// printf("executing cmd=%s\n",cmd);
fptr=open("/var/test.log",O_RDWR);
/*create new process */
child_pid = fork();
if (child_pid != 0){
/* This is the parent process. */
ret = child_pid;
//printf("c_pid=%d",child_pid);
}
else
{
/*Here is trick to direct or redirect the output to execlp*/
dup2(fptr,1);
close(fptr);
execl("/bin/sh","sh","-c",cmd,(char*)NULL);
/* The execl function returns only if an error occurs. */
fprintf (stderr, "an error occurred in execl sfdisk\n.");
exit -1;
}
//printf("done with cmd=%s child ret=%d\n",cmd,ret);

return ret;
}

The child process starts executing in another shell replacing the current process image or child;
parent process continues to execute.

if one has to wait for child to finish one can make use of wait() functions;

wait(&child_status);
if (WIFEXITED (child_status))
ret = WEXITSTATUS (child_status);
else
ret = -1;

Add this code before return statement.
In a simillar way if one needs to read input from file while using exece series function open that file in read mode and duplicate the file descriptor with stdin file descriptor.
ie simply change

dup2(fptr,0);
close(fptr);

Related questions:
use the execlp command in my C program to run the PS command and send the output into a file specified in the Argument.
Man pages for fork, open, exec and wait function.
man page for open
The fork system call creates a new child process.
The exec functions (there are more than one) are a family of functions that execute some program within the current process space.
The two versions of exec that we will be using are execlp and execvp. The difference is in the way they accept arguments, however both of them are typically called the same way.
The wait function is in and it’s a special function that allows a parent process to wait for its child processes to exit.

Comments

Popular posts from this blog

Dotnet, .Net 3.5, 2.0, C# Interview Questions

Few questions on dotnet, C# 2.0, 3.5 On Object oriented concepts 1)What is inheritance with e.g 2)What is polymorphism -function overloading -Function overriding -virtual keyword use -Static keyword and use -Abstract classes -Interface -Object 3)What is threading and how do we use in realtime application(cognizant) 4)What is threadpooling, lock, monitor(write code sample) 5)Architecture of current project 6)Session state, diffrent types of state management. 7)What is Application_Start, how it works. 8)Type of authentication in asp.net 9)How to configure ASP.NET application. 10) What is Impersonation. 11) What is WebService, WSDL, UDDI, Discovery, asmx files. 12) How to implement WebService and use it. 13) When to use WebServices. 14) WPF, how to implement(BOA) 15) Testing concvepts. 16) Test attributes 17) Flow of Automation Test Method execution 18) Features of dotnet 3.5 19) CLR, garbage collection 20) Finally block 21) Manifest, Metadata, MSIL 22) Assemblies, Type of assemblies, str...

Remote debugging for ARM target board

Remote debugging for ARM target board With GDB one can both trace and modify code and data flow, and otherwise analyze the behavior of code, without explicitly changing any of it. Rather than run a full-blown instance of GDB on the target platform, you can use GDBserver , a program that lets you run GDB on a different machine than the one on which your program is running. The advantage of using GDBserver is that it needs just a fraction of the target resources that GDB consumes, because it implements only the low-level functionality of the debugger -- namely setting breakpoints and accessing the target processor registers and read/write application memory. GDBserver takes control of the application being debugged, and then waits for instructions from a remote instance of GDB running on a development workstation. Remote target needs to have debugging stub (gdbserver), The gdbserver is also referred to as the 'stub' and must be cross-compiled for that targ...