[GE users] schedd_runlog in 6.2

Daniel Gruber D.Gruber at Sun.COM
Wed Sep 10 09:10:36 BST 2008


    [ 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. ]

A simple workaround for this issue is to
do a "qconf -w v ..." like "qconf -w v -b y date"
Because the verification (-w v) redirects the
logging and afterwards turns the logging
in schedd_runlog off. Hence the file is not growing
till the next "qconf -tsm" call.

If you are not interested in the file content
you can also delete the file and create a
soft-link with the name of that file which points
to the /dev/null device.

A bugfix is currently in work (see 
http://gridengine.sunsource.net/issues/show_bug.cgi?id=2717).

Regards, Daniel


On 09/04/08 12:07, Andy Schwierskott wrote:
> Dan,
>
> That's a problem indeed!
>
> I could verify that once you run "qconf -tsm" it's running every 
> scheduler
> interval. Also stopping/restarting the scheduler thread with "qconf 
> -ks" and
> "qconf -at scheduler" does not solve the problem:
>
> Could you please submit a CR/IZ for this bug?
>
> Andy
>
>> I just installed a 6.2 cluster with mostly default settings.  I'm 
>> noticing that my schedd_runlog file is growing quite large.  It looks 
>> like the scheduling run information is on by default.  Is anyone else 
>> seeing that behavior?
>>
>> Daniel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net
>


---------------------------------------------------------------------
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