IZ1482: ignore_fqdn=false should imply execd_spool_dir with fqdn

[uddeborg]

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

        Issue #:      1482             Platform:     All           Reporter: uddeborg (uddeborg)
       Component:     gridengine          OS:        All
     Subcomponent:    execution        Version:      6.0u3            CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     pollinger
          URL:
       * Summary:     ignore_fqdn=false should imply execd_spool_dir with fqdn
   Status whiteboard:
      Attachments:

     Issue 1482 blocks:
   Votes for issue 1482:


   Opened: Fri Mar 4 09:32:00 -0700 2005 
------------------------


Execd creates and uses a spool directory based on
it's unqualified name.  When ignore_fqdn=false is
in effect, this seems to be the wrong choice.  The
name might not be unique within the cell.  Rather,
in those cases, the execd's working directory
should have the same name as the fully qualified
domain name of the host in question.

   ------- Additional comments from andreas Thu Jun 16 09:00:53 -0700 2005 -------
Seems to have the biggest impact on install script issues.
Changing to install.

   ------- Additional comments from dom Fri Jun 17 08:07:28 -0700 2005 -------
Changed subcomponent!

If execd spooldirectory does not exist, the execd creates it with short name.
It could be a combination of install and execution.
We should ensure, that execd has no problems with fqdn spool dirs.

Marco

   ------- Additional comments from joga Tue Jun 16 05:28:10 -0700 2009 -------
That's current behaviour in SGE.
ignore_fqdn is *not* used for truncating host names, but only when comparing host names.

I agreee that truncating (or extending it by the default domain) according to ignore_fqdn would be better, but this is nothing which can be
done as a bug fix,
but only as a change in behaviour for a major release.

Making this issue an enhancement request