Re: [Condor-users] Inconsistent Disappearing Backslashes in Windows UNC Paths for Output and Error Lines

[Michael Aschenbeck <m.g.aschenbeck@xxxxxxxxx>]

Correction, this remains UNSOLVED.

On my system, the following submit file runs fine:
Universe					=	vanilla
run_as_owner				=	true
Should_transfer_files		=	YES
When_to_transfer_output		=	ON_EXIT
InitialDir					=	\\10.75.29.1\share\scratch\output
Log							=	\\10.75.29.1\share\scratch\output\initLog.log
Output						=	\\10.75.29.1\share\scratch\output\initSubmit.out
Error						=	\\10.75.29.1\share\scratch\output\initSubmit.err
Executable					=	\\10.75.29.1\share\scratch\output\simple.bat
arguments					=	10 10
Queue

On my colleagues separate system, the following submit file changes
all double backslashes to single backslashes and single backslashes to
no slashes on the Output and Error paths:
Universe					=	vanilla
run_as_owner				=	true
Should_transfer_files		=	YES
When_to_transfer_output		=	ON_EXIT
InitialDir					=	\\10.0.1.151\storage\scratch\output
Log							=	\\10.0.1.151\storage\scratch\output\initLog.log
Output						=	\\10.0.1.151\storage\scratch\output\initSubmit.out
Error						=	\\10.0.1.151\storage\scratch\output\initSubmit.err
Executable					=	\\10.0.1.151\storage\scratch\output\simple.bat
arguments					=	10 10
Queue

SAME exact paths except for the UNC drive... However, they are
formatted EXACTLY the same.  7.8.0 for my system, 7.8.3 for his
system.  Does anyone have any idea what I'm dealing with here?


On Wed, Oct 17, 2012 at 12:41 PM, Michael Aschenbeck
<m.g.aschenbeck@xxxxxxxxx> wrote:
> It never fails, as soon as I email the condor-users mailing list, I
> fix my problem.  For those of you having similar problems, here's the
> deal:
>
> We had a double backslash somewhere in the path, e.g. our submit file
> had a line that looked something like this:
>
> "Output = \\10.75.x.x\abcd\SomeFolder\\AnotherFolder\output.out"
>
> From trial and error, I found out the double backslash in the middle
> of the path (between "SomeFolder" and "AnotherFolder") was somehow
> causing Condor to decide to turn "\\" into "\" and "\" into "".  It
> would interpret the above as:
>
> "Output = \10.75.x.xabcdSomeFolder\AnotherFolderoutput.out"
>
> So the moral of the story is, make sure you don't have doubled
> backslashes, UNLESS it is the first part of a UNC path.  The following
> obviously works fine:
>
> "Output = \\10.75.x.x\abcd\SomeFolder\AnotherFolder\output.out"
>
> I do think this should be labeled as a bug in Condor, or at least
> checked when the submitter does error checking...
>
>
>
> On Wed, Oct 17, 2012 at 11:29 AM, Michael Aschenbeck
> <m.g.aschenbeck@xxxxxxxxx> wrote:
>> Hello,
>>
>> I am experiencing some very frustrating problems with how Condor is
>> interpreting my output and error lines.
>>
>> I believe it first happened after upgrading to Condor version 7.8.0.
>> I found my shadow log was turning double backslashes ("\\") into
>> single backslashes, and single backslashes were just removed.  (These
>> paths are UNC path's, e.g. \\10.75.x.x\somedir\.)  Accordingly, I
>> doubled every backslash in the output and error lines of my submit
>> file, and everything worked as expected (e.g. output =
>> \\\\10.75.x.x\\somedir\\test\\test.out)
>>
>> Later, we sent our program out the door to someone who was running
>> 7.8.3, and their system had trouble with the double backslashes..
>> They switched these to single backslashes and it worked as expected.
>> 2 months later, on the same exact system but a new program, they are
>> now having the original problem I had and double backslashes are the
>> only things that make it work!
>>
>> I have looked high and low for the reason why this is happening but I
>> can't find anything.  It is extremely frustrating, since it seems to
>> be somewhat random (they are two different submit files, but they seem
>> to have the same exact format).
>>
>> Any help/clues would be greatly appreciated!
>>
>> Thanks!
>> Mike