karthikm897 you are correct that you don't need to tie the file handle with IO::Callback. The trick there is to use the select command. On the other hand for STDERR there is a fair amount going on in the background with perl so I would reccomend either looking at the perl documentation for sigtrap or working with the special %SIG variable to target specific error message types rather than redirecting STDERR wholesale.

Hi jandrew, I tried with IO::Callback, this din't work again. try this code

use IO::Callback;

# Here's the coderef
my $code = sub {
    my $str = shift;
    print STDERR "This is really bad: $str";
};

# Turn it into a filehandle opened in write mode
my $fh = IO::Callback->new('>', $code);

# Select that filehandle (makes it the default for print, say, etc). 
select($fh);

# Print something - it gets passed to the coderef!
print "Hello World\n";
system("date");
[download]

date output doesn't get default error meta text. Also this has been mentioned in Bugs section I already have a large number of pre-written scripts and trying to capture print STDERR from them, not the system generated error signals alone. So I would like to perform similar callback function for STDERR as well. Thanks

karthikm897 I think you have an architecture problem. It appears that you are trying to splice perl into the middle of system interactions ('date' with no passed value) Whenever possible you are better off sticking to pure system calls or writing everything in perl. To choose the perl route, do some investigation around the functionality you are trying to implement not the call/response management of that functionality from the system. perl is amazingly powerful and you will probably not need a system call at all. (System calls in perl code are often categorized as "code smell")

With that said if you still want to follow system capture as a tactic, check out this stackoverflow search.