Beta 1.9 Trigger Problem

[scott]

We recently upgraded from 1.1Beta7 to 1.1Beta9. 2 triggers that previously produced no errors are now filling up the logs with errors:

({xxxxxxxx:diskfree[/].last(0)}<2000)

({xxxxxxx:memory[free].last(0)}<100m)

In researching the Free Memory trigger, I found somone that did it in percentages:

{xxxxxx:memory[free].last(0)}/{xxxxxx:memory[total].last(0)}<0.10

this requires a 2nd item to be created. Is there a better way to do these? Is there an issue with Beta1.9 that i don't know about?

Any help is greatly appreciated.