03-15-2011
Yes, that looks more like it.
I don't see that you've redirected stdout for the "w" case, so it'd go to the terminal as usual.
10 More Discussions You Might Find Interesting
1. Programming
Hi
The following is my program to test popen()
routine. The purpose is to print some contents
of the corrent directory.
But in fact, the output is only one character
'a', which I believe is the first char of the file
"a.out".
So, can anybody tell me what is wrong about
this program?... (2 Replies)
Discussion started by: dell9
2 Replies
2. Programming
hai friends
I have written a tcp chat server in c.. I have designed a cgi program in c to control it... When i try to start the server from the cgi program, it is not starting. Why is that ? I have even tried giving the root ownership for all the programs.. Still its not.
I have used the... (1 Reply)
Discussion started by: collins
1 Replies
3. Programming
Hi there,
I'm facing a problem running the tar command with the popen function.
FILE* fp = popen("tar czf - textfile","r")
// output
this program should give the output to the stdout. I don't know if it is possible and which function like fprint() etc. should I use.
I suppose that I... (4 Replies)
Discussion started by: stef83
4 Replies
4. Programming
hi,
how to work with a background process without a controlling terminal to make use of popen or system call ?
when ever i use popen or system function call in foreground process, there is no problem with respect to that .. but when the same program is run as a background process without a... (7 Replies)
Discussion started by: matrixmadhan
7 Replies
5. Shell Programming and Scripting
Hello I'm writing a web server in python(obelisk-http.sourceforge.net)
and I'm having a greeat problem with POST method it like that
When someone make a POST request to the server it must open the executable(perl/python/.exe/elf) and send to the STANDART in (stdin) the request and get the... (2 Replies)
Discussion started by: sendai
2 Replies
6. Programming
Hi!
I'm trying to write a c program. The child process must transmit to the parent a file name and the parent must count the lines from the file and return te result to the child. Here is what i've done. It doesn't stop running, I guess. I'm sorry if it's an ugly code, i'm new at this stuff,... (2 Replies)
Discussion started by: alina89
2 Replies
7. UNIX for Advanced & Expert Users
Hi
I am trying to use popen function with wrtie option to give inputs to ftp command.
#include "stdio.h"
int main(int argv ,char *argc)
{
int size=0;
char *buf;
FILE *fp;
fp = popen("ftp","w");
while(getline(&buf,&size,stdin) != -1)
write(fp,buf);... (0 Replies)
Discussion started by: kumaran_5555
0 Replies
8. Programming
hi,
i am trying to use popen to run a grep process and check if the pattern exists in the file that i am searching in. i am getting segmentation fault when i try to execute the following code
char *cd;
char flag;
char hdr_flpsp;
char hdr_flpsp2;
FILE *fp;
printf ("program starts");... (1 Reply)
Discussion started by: sais
1 Replies
9. Programming
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
10. Programming
Hello all,
I am reading a huge zip file in POPEN process and then writting that to a normal file which of 2GB. Now the process is failing when I looked for the cause someother process comming in after I read my file and it is deleting the zip. But in theory the popen command should read the... (5 Replies)
Discussion started by: arunkumar_mca
5 Replies
STDIN(3) BSD Library Functions Manual STDIN(3)
NAME
stdin, stdout, stderr -- standard I/O streams
SYNOPSIS
#include <stdio.h>
extern FILE *stdin;
extern FILE *stdout;
extern FILE *stderr;
DESCRIPTION
Under normal circumstances every Unix program has three streams opened for it when it starts up, one for input, one for output, and one for
printing diagnostic or error messages. These are typically attached to the user's terminal (see tty(4)) but might instead refer to files or
other devices, depending on what the parent process chose to set up. (See also the ``Redirection'' section of sh(1) .)
The input stream is referred to as ``standard input''; the output stream is referred to as ``standard output''; and the error stream is
referred to as ``standard error''. These terms are abbreviated to form the symbols used to refer to these files, namely stdin, stdout, and
stderr.
Each of these symbols is a stdio(3) macro of type pointer to FILE, and can be used with functions like fprintf(3) or fread(3).
Since FILEs are a buffering wrapper around Unix file descriptors, the same underlying files may also be accessed using the raw Unix file
interface, that is, the functions like read(2) and lseek(2). The integer file descriptors associated with the streams stdin, stdout, and
stderr are 0, 1, and 2, respectively. The preprocessor symbols STDIN_FILENO, STDOUT_FILENO, and STDERR_FILENO are defined with these values
in <unistd.h>.
Note that mixing use of FILEs and raw file descriptors can produce unexpected results and should generally be avoided. (For the masochistic
among you: POSIX.1, section 8.2.3, describes in detail how this interaction is supposed to work.) A general rule is that file descriptors
are handled in the kernel, while stdio is just a library. This means for example, that after an exec, the child inherits all open file
descriptors, but all old streams have become inaccessible.
Since the symbols stdin, stdout, and stderr are specified to be macros, assigning to them is non-portable. The standard streams can be made
to refer to different files with help of the library function freopen(3), specially introduced to make it possible to reassign stdin, stdout,
and stderr. The standard streams are closed by a call to exit(3) and by normal program termination.
SEE ALSO
sh(1), csh(1), open(2), fopen(3), stdio(3)
CONSIDERATIONS
The stream stderr is unbuffered. The stream stdout is line-buffered when it points to a terminal. Partial lines will not appear until
fflush(3) or exit(3) is called, or a newline is printed. This can produce unexpected results, especially with debugging output. The buffer-
ing mode of the standard streams (or any other stream) can be changed using the setbuf(3) or setvbuf(3) call. Note that in case stdin is
associated with a terminal, there may also be input buffering in the terminal driver, entirely unrelated to stdio buffering. (Indeed, nor-
mally terminal input is line buffered in the kernel.) This kernel input handling can be modified using calls like tcsetattr(3); see also
stty(1), and termios(3).
CONFORMING TO
The stdin, stdout, and stderr macros conform to ANSI X3.159-1989 (``ANSI C89''), and this standard also stipulates that these three streams
shall be open at program startup.
Linux 2.0 March 24, 1998 Linux 2.0