Opened 15 years ago

Last modified 9 years ago

#209 new enhancement

IZ1326: Default qstat output should not exceed 80 columns

Reported by: andreas Owned by:
Priority: normal Milestone:
Component: sge Version: 6.0
Severity: Keywords: clients
Cc:

Description

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

        Issue #:      1326             Platform:     All           Reporter: andreas (andreas)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.0              CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     roland
          URL:
       * Summary:     Default qstat output should not exceed 80 columns
   Status whiteboard:
      Attachments:

     Issue 1326 blocks:
   Votes for issue 1326:


   Opened: Wed Nov 10 11:28:00 -0700 2004 
------------------------


qstat now runs to 112 columns - not good for users
with standard 80-column displays. A couple of ways
to rationalise this:

   - the FQDN of an execution host isn't really
necessary, even on systems with execution hosts in
different domains, and it takes up a good few chars

   - the year part of the submission/start date
could be removed, as I can't imagine many users
having year-long jobs (though of course it needs
to preserved for qacct output)

    - the task id field takes up a lot space
simply because of the field name, the rather
lengthy "ja-task-ID"

   ------- Additional comments from andreas Wed Nov 10 11:42:53 -0700 2004 -------
I fear the domainname can be omitted only if there remains a means to
request FQDN still be shown. For this qstat output customization would
be needed. See also issue #77.


   ------- Additional comments from sgrell Mon Dec 12 02:41:37 -0700 2005 -------
Changed subcomponent.

Stephan

Change History (0)

Note: See TracTickets for help on using tickets.