Chris Sheffield wrote:
> I failed to mention that I have this line of code in my startup
> handler. Not sure if that's required or not. Might be okay to have
> it in preOpenStack as well.
>
> On Jan 28, 2010, at 8:36 AM, Chris Sheffield wrote:
>
>> Hi Sarah,
>>
>> I believe this is the workaround we used:
>>
>> set the revruntimebehaviour to 4
>>
>> I honestly don't remember the details behind this. It might
>> be documented in the bug ticket (7290 or 6343). I think this
>> is an undocumented property, and I'm not entirely sure what
>> the value 4 means. Sorry for being rather vague. It's also
>> possible that this line of code came to me as a result of
>> emailing support directly.
It's in
<http://quality.runrev.com/qacenter/show_bug.cgi?id=6235>
Leading us to two questions:
1. What is revruntimebehaviour? What happens if we set it to 5? or 100?
Or 4444?
2. If this is easily rectified with a one-line call to a global
property, couldn't this be done in the engine sometime in the last four
releases since it was reported?
--
Richard Gaskin
Fourth World
Rev training and consulting: http://www.fourthworld.com
Webzine for Rev developers: http://www.revjournal.com
revJournal blog: http://revjournal.com/blog.irv
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
