CLT - Get File Locations Problem

TS 6.5 sp1, Win 2003

I am trying to get the TS config file/log file locations.

my $cmd = "D:\iw-home\bin\iwgetlocation.exe -a";
my @fileLoc = `$cmd`;

But this is giving error like(Error.log) :
'The filename, directory name, or volume label syntax is incorrect.\n'

The output from command line is

iwhome=D:\iw-home
..........................................
iwmount=Y:
iwcgimount=Y:
..........................................

Is there any wrong in the command usage? Thanks for your help.

Sri

Find more posts tagged with

Comments

Migrateduser

Yes, because you're on a Windows platform, you'll need to escape the backslash (\\ instead of \). Sometimes, however, you can get away with using a forward slash but I'm not sure what the science is behind that.

Personally, I'd like to beat the **** out of the guy at Microsoft (presumably) who came up with the backslash delimiter, after decades of perfectly productive Unix (and other) machines had been operating happily with the forward slash. How many hours of productivity has it cost us with issues like this?

Okay, sorry for my rant. I've got to keep that to a minimum, really.

No, Jeff, I'm not smoking crack.

Srinivasa Talla

Thanks. Just I put the reverse slash. I got it. Your response also usefull.

Adam Stoller

Yes, because you're on a Windows platform, you'll need to escape the backslash (\\ instead of \). Sometimes, however, you can get away with using a forward slash but I'm not sure what the science is behind that.

Personally, I'd like to beat the **** out of the guy at Microsoft (presumably) who came up with the backslash delimiter, after decades of perfectly productive Unix (and other) machines had been operating happily with the forward slash. How many hours of productivity has it cost us with issues like this?

Okay, sorry for my rant. I've got to keep that to a minimum, really.

No, Jeff, I'm not smoking crack.

I'd say that in about 99% of the cases you can use forward slashes instead of single or double backslashes. In the case of back-ticks (`...`) or qx(...) - the contents of the statement are interpolated which means that you either need to use double-backslashes or single forward slashes - or something hokey like:

`q(d:\iw-home\bin\iwgetlocation -a)`

- but I think you're generally better off always using forward slashes.

Some useful code tidbits:

...
use TeamSite::Config;
my $iwmount = TeamSite::Config::iwgetmount();
my $iwhome = fix_path(TeamSite::Config::iwgethome());
...
sub fix_path{
    (my $path = shift) =~ tr|\\|/|; # use forward-slashes
    $path =~ s|^//[^/]+||;          # remove server-specific vpath prefix, if present
    $path =~ s|^$iwmount||;         # remove iwmount prefix if present, add it back explicitly where/when necessary
    return $path;
}

If you use fix_path() wherever you first encounter a path value - you'll always know the format of the string after that (it will either be a full vpath or a relative path with forward-slashes) - which makes it much easier to construct regex's that deal with paths later in the code.

nipper

This is soooo fun:



my $iwhome = fix_path(TeamSite::Config::iwgethome();


should be 

my $iwhome = fix_path(TeamSite::Config::iwgethome());