C, UNIX: How to redirect 'stdout' to a file from a C code?


 
Thread Tools Search this Thread
Top Forums Programming C, UNIX: How to redirect 'stdout' to a file from a C code?
# 1  
Old 10-13-2016
C, UNIX: How to redirect 'stdout' to a file from a C code?

I am looking for a way to redirect standard output to a file from a C-code;
so, any 'cout<<..' or 'printf(...)' will be written into a file.

I have a server source that I need to debug.
That program called by RPC (remote procedure call) and has no any session to print out anything.
I have some my source with set of macro and functions that are useful for debugging any source; but, it is writing into the standard output.

Therefore I would like to redirect the stdout to a file to use those debug-tools into the server source.

How that could be done?

Thanks.
# 2  
Old 10-13-2016
Here is sample code using dup() and dup2()- I copied this from somewhere years ago:
Code:
#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <unistd.h>

int main(int argc, const char *argv[])
{
    int out = open("cout.log", O_RDWR|O_CREAT|O_APPEND, 0600);
    if (-1 == out) { perror("opening cout.log"); return 255; }

    int err = open("cerr.log", O_RDWR|O_CREAT|O_APPEND, 0600);
    if (-1 == err) { perror("opening cerr.log"); return 255; }

    int save_out = dup(fileno(stdout));
    int save_err = dup(fileno(stderr));

    if (-1 == dup2(out, fileno(stdout))) { perror("cannot redirect stdout"); return 255; }
    if (-1 == dup2(err, fileno(stderr))) { perror("cannot redirect stderr"); return 255; }

    puts("doing an ls or something now");

    fflush(stdout); close(out);
    fflush(stderr); close(err);

    dup2(save_out, fileno(stdout));
    dup2(save_err, fileno(stderr));

    close(save_out);
    close(save_err);

    puts("back to normal output");

    return 0;
}

From your description it does not sound like this will help you.
These 2 Users Gave Thanks to jim mcnamara For This Post:
# 3  
Old 10-13-2016
Thank you, jim mcnamara, it is perfectly helps!
Sure here is more than I need in my case, but everything is clear and strait forward!
Additionaly, your code keep a way to switch back that not needed right now, but could be a task later on such approach!

Also I've found useful (by another reply) the 'freopen()' C-function and did it in very simple way, too.
(... for anybody else with the same task and for myself later, here is how I did it with freopen() ) :
Code:
#include <iostream>
#include <fstream>
#include <stdio.h>

using namespace std;

void redir(char* fl_nm)
{
  freopen(fl_nm,"a",stdout);
}

int main()
{
   cout << "starting - by cout\n";
   printf(" this written by printf()\n Following messages shoul go to the file '/tmp/tst_redir.log'\n");

   redir((char*)"/tmp/tst_redir.log");

   cout << ".. By 'cout' after using the redir(): this should be written to the file\n";
   printf(" .. By printf() after 'redir()'...\n");

  return 0;
}

But, again, thanks for your solution!!
# 4  
Old 10-13-2016
freopen DOES NOT redirect standard output! You are only redirecting the C file pointer 'stdout', not the file descriptor it uses.

Basically, you're ripping the floor out from under your program without guaranteeing that the Right Thing has happened to put a new floor back. The 'stdout' file pointer will continue to work, but anything not informed of the change might not -- like cout, and any subprocesses you happen to run. Their output may not go where you expected, or go nowhere at all, or crash. It might work right, if the next file opened happens to land at file descriptor 1 -- or it might not. The behavior is undefined and at the mercy of what libraries and compiler you're using. All that's guaranteed after you do that is that stdio routines like printf() will go where you redirected.

Whatever file descriptor 1 went to before, might not be properly closed after freopen, either. If stdout was an open file descriptor to a terminal preventing your ssh window from closing, such is life.

The "right thing" to do if you really want to redirect "standard output", not just the stdio external variable "stdout", is to ensure that the file you want is opened specifically as file descriptor one, which is what dup2() does in the example you were given. Which is much simpler than it looks once you realize it's redirecting twice: Once for stdout, once for stderr. Re-opening onto file descriptor one with dup2() also guarantees that whatever was there before, is forced to close. This could be especially important if that happened to be a terminal or device file.

Also, your example is concerning. Never mix printf and cout, for starters, especially if you're going to play funny games with redirection.

Last edited by Corona688; 10-13-2016 at 08:04 PM..
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Redirect STDOUT & STDERR to file and then on screen

Dear all, redirecting STDOUT & STDERR to file is quite simple, I'm currently using: Code: exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.log But during script execution I would like the output come back again to screen, how to do that? Thanks Luc edit by bakunin: please use CODE-tags like the... (6 Replies)
Discussion started by: tmonk1
6 Replies

2. Shell Programming and Scripting

Redirect STDOUT & STDERR to file and then on screen

Dear all, redirecting STDOUT & STDERR to file is quite simple, I'm currently using: exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.logBut during script execution I would like the output come back again to screen, how to do that? Thanks Lucas (4 Replies)
Discussion started by: Lord Spectre
4 Replies

3. UNIX for Dummies Questions & Answers

STDOUT redirect to file and format problems

Hi All, I am using centOS. When I try to redirect STDOUT to a file, it ends up in getting some funny characters. For example ... STDOUT of the command as follows. $ ls H3k27me3 H3k36me3 H3k4me1 H3k4me2 H3k4me3 H3k9ac H4k20me1 $ ls >test $ cat test ^ (1 Reply)
Discussion started by: Chulamakuri
1 Replies

4. Shell Programming and Scripting

redirect stdout and stderr to file wrong order problem with subshell

Hello I read a lot of post related to this topic, but nothing helped me. :mad: I'm running a ksh script with subshell what processing some ldap command. I need to check output for possible errors. #!/bin/ksh ... readinput < $QCHAT_INPUT |& while read -p line do echo $line ... (3 Replies)
Discussion started by: Osim
3 Replies

5. Shell Programming and Scripting

redirect STDOUT to a file in a subshell

Hi, I would like to avoid re-directing line by line to a file. What is the best way to re-direct STDOUT to a file in a subshell? Thanks in advance. Cheers Vj (1 Reply)
Discussion started by: tnvee
1 Replies

6. Shell Programming and Scripting

Redirect stdout/stderr to a file globally

Hi I am not if this is possible: is it possible in bach (or another shell) to redirect GLOBALLY the stdout/stderr channels to a file. So, if I have a script script.sh cmd1 cmd2 cmd3 I want all stdout/stderr goes to a file. I know I can do: ./script.sh 1>file 2>&1 OR ... (2 Replies)
Discussion started by: islegmar
2 Replies

7. Programming

redirect stdout

hello again! i use dup2 to redirect stdout. I run what i want, now i want undo this redirection. how can i do that? thanx in advance (7 Replies)
Discussion started by: nicos
7 Replies

8. Shell Programming and Scripting

How to redirect stderr and stdout to a file

Hi friends I am facing one problem while redirecting the out of the stderr and stdout to a file let example my problem with a simple example I have a file (say test.sh)in which i run 2 command in the background ps -ef & ls & and now i am run this file and redirect the output to a file... (8 Replies)
Discussion started by: sushantnirwan
8 Replies

9. UNIX for Advanced & Expert Users

STDOUT redirect to a FILE, when fuser command is used !!

Hi all, I have the following script: ------------------------------------------------- #SCRIPT TO CHECK WHO HAS ACCESSED THE LOG/FILE IN PAST 'N' MINUTES, AND MAIL ACCORDINGLY. MYPATH="/clocal/mqbrkrs/user/mqsiadm/sanjay/" MAIL_RECIPIENTS="vg517@dcx.com" Subject="File accessed in last... (6 Replies)
Discussion started by: varungupta
6 Replies

10. UNIX for Advanced & Expert Users

problem with redirect stdout to file

Hi all hope you can help as I am going MAD!!! :eek: The below is in a shell script but the redirection in the sed line does not work and outputs to the screen and the $fname_2 does note get created ????? Can any one help ?? #!/bin/ksh cd /app/ for fname in `ls -1 X*` do sed 1d $fname... (3 Replies)
Discussion started by: mlucas
3 Replies
Login or Register to Ask a Question