Opened 14 years ago

Last modified 9 years ago

#239 new defect

IZ1555: No options are allowed after quotes

Reported by: templedf Owned by:
Priority: low Milestone:
Component: sge Version: 6.0
Severity: Keywords: clients
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=1555]

        Issue #:      1555             Platform:     All      Reporter: templedf (templedf)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.0         CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    templedf (templedf)
      QA Contact:     roland
          URL:
       * Summary:     No options are allowed after quotes
   Status whiteboard:
      Attachments:

     Issue 1555 blocks:
   Votes for issue 1555:


   Opened: Mon Apr 11 08:19:00 -0700 2005 
------------------------


The string_list() function, which is used throughout Grid Engine to parse a
string into an array of strings, does not recognise closing quotes.  This means
that everything after the first quote is considered a single argument,
regardless of whether a closing quote appears.

For example, if a script contains the following:

#$ -sync "y" -N Bob

running the script will produce:

% qsub /tmp/auto/examples/jobs/exit.sh
Unable to read script file because of error: invalid option argument "-sync """
-N Bob"

The work-around would be to always divide options with quote onto separate lines.

   ------- Additional comments from templedf Tue Oct 25 16:05:48 -0700 2005 -------
Taking over.

   ------- Additional comments from templedf Tue Oct 25 16:10:21 -0700 2005 -------
Dropping priority according to Andy:

Has not been detetect by any customers over the years.

   ------- Additional comments from sgrell Tue Dec 6 03:59:50 -0700 2005 -------
Changed subcomponent.

Stephan

Change History (0)

Note: See TracTickets for help on using tickets.