Programming

Herez the question,

In a process which writes into file FILE1 with descriptor
fHandler1 and it is run as a background process
where would statements be directed
when stderr descriptor is used.

fprintf(stderr,"some message\n");

assume that session from which it is run is terminated and later the above statement is executed.

Are there any chances for output given to stderr descriptor to be redirected
to the fHandler1...

because in one of our process, i could specifically see redirections are in a perplexed manner

fHandler1=fopen("ping.con","a");
fprintf(fHandler,"first segment\n);
fprintf(stderr,"errored value\n");

i am surprised to see the output errored value in the file ping.con

please let me know if i had to provide any more information.

I put your code in a C program. Here it is:

Code:

#include<stdio.h>

int main(void) {

   FILE *fHandler1;

   fHandler1=fopen("ping.con","a");
   fprintf(fHandler1,"first segment\n");
   fprintf(stderr,"errored value\n");
   fclose(fHandler1);
}

This worked fine. When I ran it, ping.con was created and the line "first segment" was written in and the string "errored value" was output to the stderr (on screen).

Unless you are running the program as './program_name 2>>ping.con ' or assigning the value of fHandler1 to stderr at some point in the program, "errored value" should not be output to ping.con.

thanks for the reply,

the code that u tried seems to work fine
this is what even i tried in my code and it worked perfectly
as expected

first message to be sent to file with fHandler
and the second to the stderr (stderr)

i am sure no where errors are redirected and file handlers
mishandled but still the problem exists

i would like to remind u, i am not sure whether there is any hint in that
the session from where the program is run would be terminated.

as in this sequence

program boots
string directed to file
session terminates
string directed to 2 stderr
processing continues

i dont see any acceptance with the scenario
but still problems faints to perish
and i am looking out for the reason.

Does the file ping.com exist before the program opens it? Maybye it's a named pipe...