[GE users] SGE 6.0 - qmon queue values reverting to default

Walt Minkel wminkel at latticesemi.com
Fri Apr 22 15:52:51 BST 2005

    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "ISO-8859-10" character set.  ]
    [ Some special characters may be displayed incorrectly. ]

Hi Dan,

I understand how the padlocks work and they are not the problem.
Upgrading to 6.0u3 might fix the problem.

Thanks for your response.

Dan Gruhn wrote:

> Hi Mike,
> I am using 6.0u3 on Linux and don't see this happen when the 
> particular field is unlocked.  However, if I change the number of 
> slots for a particular host and then lock the entry, it reverts back 
> to the default value.  I have just assumed the one has to leave the 
> field unlocked if one wants a different value from the default.
> Is this what is happening to you?
> Dan
> On Thu, 2005-04-21 at 19:55, Walt Minkel wrote:
>>/Hi All,
>>In SGE 6.0u1 on  Solaris 8.
>>In a cluster queue, all in the same qmon session:   If after looking at 
>>queue's values that are
>>different than the @/ (default), I exit the modify cluster form by 
>>clicking "cancel",  the next
>>time I modify the cluster all of the values for that queue have reverted 
>>to the default. 
>>If I cancel and exit out of qmon, then re-open qmon,  the values return 
>>to their state before
>>the cancel the original cancel.
>>For example, if a cluster's default is 5 slots per host except for one 
>>host which has 10 slots.
>>If after browsing around that hosts forms,  I cancel.  The host will 
>>show 5 slots the next
>>time I call it up (all within the same qmon session).
>>It appears like the qmon gui is not in-sync with files in the spool 
>>Have other seen this?  Is there a patch?
>>     Walt
>>To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>>For additional commands, e-mail: users-help at gridengine.sunsource.net

More information about the gridengine-users mailing list