Sponsored Content
Top Forums Programming Question about system command in C Post 302505768 by Corona688 on Thursday 17th of March 2011 05:16:50 PM
Old 03-17-2011
You should also put the sigprocmask/sigaction resets in the { perror("fork failed"); exit(-1); } section, otherwise you won't reset them when fork throws an error. Otherwise, it looks OK now. Smilie
 

9 More Discussions You Might Find Interesting

1. IP Networking

I have some question on unix system

Dear all, If I login to a Unix system (general user account), will the unix system generate a history file? If positve, will it stored the IP adress also? Thanks and Regards Penny Li ;) (2 Replies)
Discussion started by: PennyLi
2 Replies

2. UNIX for Dummies Questions & Answers

solaris File system question ( UFS )

Hello all, I'm ufs file system, how can u use the same disk in another machine with the data in tact? to make it clear, I've an ufs FS in a mount point /file1 ( 8GB). now they decide to reintall the OS. After the reinstall, how can i get the same data as it is? will mounting the disk as /file1... (3 Replies)
Discussion started by: i2admin
3 Replies

3. Programming

Question about the system() function in C

Hello all ! Could someone throw some light on whether there's a limit to the number of characters contained in the command string that is passed to the system() call in C. Is it OS dependent? If yes, what are the limits for each? Thanks. (4 Replies)
Discussion started by: vsanjit
4 Replies

4. Solaris

File system - question?

Hello, I have few questions about file system in Unix and Linux. 1. What's the difference between Unix and Linux in their file system? Are they the same? 2. Is in Unix directory for administrator "/root" - like in Linux - Ubuntu or not? 3.Where is the users directory in Unix? Is it... (2 Replies)
Discussion started by: niki22
2 Replies

5. Programming

question about system and popen in C

in man system it talks about SIGCHLD will be blocked, and SIGINT and SIGQUIT will be ignored. Does this signal stuff also happen in popen command? (even though man popen says nothing about signals) also if I am not using wait(&status) and I am using waitpid(pid, NULL, 0) how would... (1 Reply)
Discussion started by: omega666
1 Replies

6. Shell Programming and Scripting

System Command dies even when command gets executed successfully

Hi I have created a perl script & running it using Linux machine. I want my script to die when system command is unsuccessful but script is dying even when system command gets executed successfully. :wall: I am using the command below :- system($cmd) || die "FAILED $!"; print "Hello"; ... (2 Replies)
Discussion started by: Priyanka Gupta
2 Replies

7. UNIX for Dummies Questions & Answers

Unix directory system calls question

I'm currently studying for my exam, and is practicing with sample exam questions. However there is a question asking "Name THREE UNIX Directory system calls" and the answer given is "opendir, closedir and readdir", however the next question ask "Why is a write directory system call not included... (1 Reply)
Discussion started by: Izzy123
1 Replies

8. UNIX for Dummies Questions & Answers

question about unix file system

Hi, The file system unix use a multilevel indexes access to disk, 12 direct blocks, 1 single indirect block, 1 double indirect block, 1 triple indirect block: Assuming a: block = 512 bytes, pointer = 4 byte, and there is a file of 200 blocks, how many disk access is needed to read the block... (1 Reply)
Discussion started by: blob84
1 Replies

9. UNIX for Dummies Questions & Answers

Question on Veritas file system..

Hi, I am on Solaris 10 server which is running Veritas. It's E420 server with two drives. I don't know much about Veritas. The other guy who works on this, on vacation this week. :-) Any way, looks like I have hard drive issue on the server. When I do iostat -E. I see this. sd0... (4 Replies)
Discussion started by: samnyc
4 Replies
system(3C)						   Standard C Library Functions 						system(3C)

NAME
system - issue a shell command SYNOPSIS
#include <stdlib.h> int system(const char *string); DESCRIPTION
The system() function causes string to be given to the shell as input, as if string had been typed as a command at a terminal. The invoker waits until the shell has completed, then returns the exit status of the shell in the format specified by waitpid(3C). If string is a null pointer, system() checks if the shell exists and is executable. If the shell is available, system() returns a non-zero value; otherwise, it returns 0. The standard to which the caller conforms determines which shell is used. See standards(5). The system() function sets the SIGINT and SIGQUIT signals to be ignored, and blocks the SIGCHLD signal for the calling thread, while wait- ing for the command to terminate. The system() function does not affect the termination status of any child of the calling processes other than the process it creates. The termination status of the process created by the system() function is not affected by the actions of other threads in the calling process (it is invisible to wait(3C)) or by the disposition of the SIGCHLD signal in the calling process, even if it is set to be ignored. No SIGCHLD signal is sent to the process containing the calling thread when the command terminates. RETURN VALUES
The system() function executes posix_spawn(3C) to create a child process running the shell that in turn executes the commands in string. If posix_spawn() fails, system() returns -1 and sets errno to indicate the error; otherwise the exit status of the shell is returned. ERRORS
The system() function may set errno values as described by fork(2), in particular: EAGAIN A resource control or limit on the total number of processes, tasks or LWPs under execution by a single user, task, project, or zone has been exceeded, or the total amount of system memory available is temporarily insufficient to duplicate this process. ENOMEM There is not enough swap space. EPERM The {PRIV_PROC_FORK} privilege is not asserted in the effective set of the calling process. USAGE
The system() function manipulates the signal handlers for SIGINT and SIGQUIT. It is therefore not safe to call system() in a multithreaded process, since some other thread that manipulates these signal handlers and a thread that concurrently calls system() can interfere with each other in a destructive manner. If, however, no such other thread is active, system() can safely be called concurrently from multiple threads. See popen(3C) for an alternative to system() that is thread-safe. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
ksh(1), sh(1), popen(3C), posix_spawn(3C), wait(3C), waitpid(3C), attributes(5), standards(5) SunOS 5.11 14 Dec 2006 system(3C)
All times are GMT -4. The time now is 05:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy