Sponsored Content
Top Forums Programming alternatives of exec() system function Post 302155100 by Raj Kumar Arora on Thursday 3rd of January 2008 01:20:02 AM
Old 01-03-2008
Quote:
Originally Posted by porter
fork and exec are two of the most fundamental calls on a UNIX system, if these are failing the system won't work.

Any alternative, such as "system()" or "popen()" will call fork()/vfork() and exec(), there is not really any other portable way to start a new process and launch a new program in it.

I suggest the errors are in the usage or understanding of what these calls do.

Admittedly, Linux has clone() but that's another story.
Thanks porter for your reply. The problem is not exactly in usage because it is running at few machines too. It may be some sort of environment or previledges problem. Actually now the situation is that I am trying to do that using Multithreading. I am creating two threads.

I needed to call an executable with some arguments in the function body for second thread. For that I am using system() call.

The problem is that :-
1. system() function call is not allowing any further arguments to executable being called as execl() would if I was using a fork()-execl() pair in case of Multiprocessing.

2. I need alternative to system() because system is also creating a new process. And I dont want to create a new process in a thread.

Regards,
Raj Kumar Arora
 

10 More Discussions You Might Find Interesting

1. Programming

exec() system call

hi there, i was reading about the exec() function. and if i m not wrong, exec() kills your present process and starts a new process in its place. the process id remains the same. then it says if exec is successful the text data and stack are overlayed by new file! - i dont get this part "only... (2 Replies)
Discussion started by: a25khan
2 Replies

2. UNIX for Advanced & Expert Users

Alternatives to set the system date ??

Hi all, I need to syncronize a Solaris client with a QNX Server, modifying the client date, I need any alternative to set the sistem date (client Solaris) but i can't use commands date -a XXX (XXX are the time in seconds) and can't use rdate and ntp. How can I do It? :confused: (2 Replies)
Discussion started by: ulisses0205
2 Replies

3. Shell Programming and Scripting

How can I execute own ksh function in find -exec

Hi, I wrote a smiple ksh function send_notification() { ... } and want to execute it on each file, matched by the find command. I tried: find / -name "*.err" -mtime -8 -exec send_notification {} \; but it doesn't work. What should I do? I work in ksh on Hp-Ux. Regards, Pit (11 Replies)
Discussion started by: piooooter
11 Replies

4. UNIX for Advanced & Expert Users

exec to call specific function in C prog

I would like to call a particular function in a C program using execl(). Is this possible using execl or anyother function ? Thanks (2 Replies)
Discussion started by: vpraveen84
2 Replies

5. Programming

Runtime.getSystem.exec() function waits for child

Runtime.getSystem.exec() waits for child process to complete .. I do not want to wait for the child process to complete ..what is the option which has to be used ? (2 Replies)
Discussion started by: shafi2all
2 Replies

6. Shell Programming and Scripting

How to execute piped command using exec or system

Hi All, I want to execute a piped command like 'ls /opt | grep xml' using array as parameters list. How can I do that? (2 Replies)
Discussion started by: bharadiaam
2 Replies

7. Shell Programming and Scripting

Perl variables in exec or system

I am new in Perl. I am working in simple script and the varibles are working well outside the exec or system command. but they don't work as parameters to exec or system command. The script is attached. please help. (8 Replies)
Discussion started by: ahmed_zaher
8 Replies

8. UNIX for Dummies Questions & Answers

Using system function in C

Hi Guys , I want to use system function in C to do the following work. cp <file1> <file2> and then ><file1> e,g cp \var\log\cpm_cpmd_1.log.1 \var\log\cpm_cpmd_1.log.2 and then >\var\log\cpm_cpmd_1.log.1 1. g_config_info.cpmm_config.cpm_log_path=\var\log\ 2. ... (3 Replies)
Discussion started by: meet123321
3 Replies

9. Programming

[C] exec system call

Hi again ;) Now I want to make a program that will execute the programs with exec, asking the user if he wants the program to run in background or foreground. scanf("%c",&caracter); if (caracter=='y'){ printf("Has decidido ejecutarlo en background\n"); if((pid=fork())==0) {// fork para... (3 Replies)
Discussion started by: lamachejo
3 Replies

10. Shell Programming and Scripting

Script Variables Inquiry, Values Okay in Standalone Exec, No-Show in Cron Exec

I have the following bash script lines in a file named test.sh. #!/bin/bash # # Write Date to cron.log # echo "Begin SSI Load $(date +%d%b%y_%T)" # # Get the latest rates file for processing. # d=$(ls -tr /rms/data/ssi | grep -v "processed" | tail -n 1) filename=$d export filename... (3 Replies)
Discussion started by: ginowms
3 Replies
EXEC(2) 							System Calls Manual							   EXEC(2)

NAME
exec, execl, _clock - execute a file SYNOPSIS
#include <u.h> #include <libc.h> int exec(char *name, char* argv[]) int execl(char *name, ...) long *_clock; DESCRIPTION
Exec and execl overlay the calling process with the named file, then transfer to the entry point of the image of the file. Name points to the name of the file to be executed; it must not be a directory, and the permissions must allow the current user to execute it (see stat(2)). It should also be a valid binary image, as defined in the a.out(6) for the current machine architecture, or a shell script (see rc(1)). The first line of a shell script must begin with followed by the name of the program to interpret the file and any initial arguments to that program, for example #!/bin/rc ls | mc When a C program is executed, it is called as follows: void main(int argc, char *argv[]) Argv is a copy of the array of argument pointers passed to exec; that array must end in a null pointer, and argc is the number of elements before the null pointer. By convention, the first argument should be the name of the program to be executed. Execl is like exec except that argv will be an array of the parameters that follow name in the call. The last argument to execl must be a null pointer. For a file beginning #!, the arguments passed to the program (/bin/rc in the example above) will be the name of the file being executed, any arguments on the #! line, the name of the file again, and finally the second and subsequent arguments given to the original exec call. The result honors the two conventions of a program accepting as argument a file to be interpreted and argv[0] naming the file being exe- cuted. Most attributes of the calling process are carried into the result; in particular, files remain open across exec (except those opened with OCEXEC OR'd into the open mode; see open(2)); and the working directory and environment (see env(3)) remain the same. However, a newly exec'ed process has no notification handler (see notify(2)). When the new program begins, the global cell _clock is set to the address of a cell that keeps approximate time expended by the process at user level. The time is measured in milliseconds but is updated at a system-dependent lower rate. This clock is typically used by the profiler but is available to all programs. The above conventions apply to C programs; the raw system interface to the new image is as follows: the word pointed to by the stack pointer is argc; the words beyond that are the zeroth and subsequent elements of argv, followed by a terminating null pointer; and the return register (e.g. R0 on the 68020) contains the address of the clock. Alef In Alef, the intent and syntax are the same but the implementation is different. Exec (or execl; this description applies to either) may be called only by a proc holding a single task, typically the implicit main task of the proc. First, access(2) is called to see if the named file exists and has execute permission. If not, exec returns -1 immediately. Otherwise, it will never return: it frees resources private to the invoking proc and calls the exec system call. If this fails, it calls the bare _exits system call (see exits(2)) with the error string as argument. Therefore, if the file looks executable, the calling process is lost, whether the exec succeeds or not. SOURCE
/sys/src/libc/9syscall /sys/src/libc/port/execl.c SEE ALSO
intro(2), stat(2) DIAGNOSTICS
If these functions fail, they return and set errstr. There can be no return from a successful exec or execl; the calling image is lost. EXEC(2)
All times are GMT -4. The time now is 04:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy