require File::Spec;
my $devnull = File::Spec->devnull();
my $cmd = `cleartool ls -l $fname 2>$devnull`;
[download]

Thanks !!
It works.
This is the first time I posted a question here, and already it was worth it !
Keep up the good work :)

You might wish to investigate these modules for future use:

IPC::ClearTool
ClearCase::Proc::ClearTool
ClearCase::CtCmd
ClearPerl: Perl 5 modules for ClearCase

For a slightly more complicated, but platform agnostic (I do like that expression - thanx again bart) solution, why not try...

find({wanted => \&viewscan,follow}, $view);

sub viewscan
{
    open CMD, "cleartool ls -l $fname 2>&1 |", or die(...);
    my @fileinfo = <CMD>;
    close CMD;
    @fileinfo = grep /view private/, @fileinfo;
}
[download]

find({wanted => \&viewscan,follow}, $view);

sub viewscan
{
    open CMD, "cleartool ls -l $fname 2>&1 |", or die(...);
    my @fileinfo = grep /view private/, (<CMD>);
    close CMD;
}
[download]

HTH ,

You can find more information on the backticks from "perldoc perlop" (look for "qx"). Quote: "The collected standard output of the command is returned; standard error is unaffected." It then goes on to give a bunch of examples, including the answer to your question.

I think there are a few reasons for this behaviour. First off, you generally don't want to hide the stderr. If there is an error in the command you're running, you probably DO want it to leak through to the person running the script - it may have very useful information as to why your code is acting funny. Second, it serves as a reminder to us, the perl developers, that there's really nothing we can do to block all output. If an application really wants to, it can open a brand new filehandle to the current (pseudo-)terminal device, which seems really easy on Linux - get your parent's pid, and open /proc/$ppid/fd/1 for writing:

$ perl -le 'open my $fh, ">", "/proc/" . getppid . "/fd/1" or die $!;p
+rint $fh "<Nelson>Ha ha!</Nelson>"' > /dev/null 2> /dev/null
<Nelson>Ha ha!</Nelson>
[download]

my $returned = `YOUR_COMMAND_HERE 2>/dev/null`;
[download]

It looks like you are trying to write your own version of the lsprivate cleartool command.

cleartool lsprivate [/vobs/whatever/path/you/like]

When you run it with no path, it will show all private files in your view. When you run it with a path, it will only show you the private files in your view in that portion of the directory tree.

It looks like you are trying to write your own version of the lsprivate cleartool command.

Clippy, is that you?

It can't be Clippy, the response was helpful and insightful. It must really be Mr. Muskrat.


TGI says moo