Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [Fwd: Re: [geclipse-dev] g-Eclipse pre-release build] 


On Tue, 25 Sep 2007, Ashish Thandavan wrote:


Hi Szymon,

Well spotted! Apologies everyone, the earlier problem I reported was due
to 'User Error' :-) I can now submit to both iwrrb and wms103.


I was just writing explanation of the problem, too. :)

So, some bacground of this error:

And in fact you can use \ but in this case it must be escaped by another \

\\bin\\hostname.
It will be accepted, but not working, because there is no command "\bin\hostname" on Unix. 

I am not sure how we should handle such errors.
It is not error from the point of view of XML. XML allows "\" characters.
And in fact on the client part this XML was handled correctly by XML parser while translating JSDL to JDL. 

The problem is on the server side and only for single \ in Executable.
JobName and ApplicationName can contain \ and it is not a problem for server side XML parser. I guess it is caused by using shell scripts inside JDL parser to create executable JOB script.
The problem is not in the "\" character itself, but in special meaning of some escape sequences. 
Shell uses some special characters:
              \a     alert (bell)
              \b     backspace
              \e     an escape character
              \f     form feed
              \n     new line
              \r     carriage return
              \t     horizontal tab
              \v     vertical tab
              \\     backslash
              \'     single quote
              \nnn   the eight-bit character whose value  is  the
                     octal value nnn (one to three digits)
              \xHH   the  eight-bit  character whose value is the
                     hexadecimal value HH (one or two hex digits)
And in fact if commandline is \min\hostname, there is not SAX parser error while submission. But it causes another submission error because command "minhostname" is not found.
I am definitely against automatic correction of "\" to "/". Some strange command names can have "\" inside and it could be exactly what user wanted to enter.
I can add description of the error like "Check if your executable is correct". But sometimes it can confuse user because the same error can be caused by many different reasons.
It also cannot be prevented by checking for "\" in jsdl, because maybe for some grids it would be possible to submit jsdl to windows machine. 

Regards,

Pawel

Back to the top