Odd behaviour of Netsaint 0.0.7

We've been trying to set up a system to upgrade to 0.0.7, but have come
across a couple of oddities.

1) When the "aggregate write" option is on, NetSaint seems to "forget" to
write out the status.log file. I set the aggregate write delay to 10
seconds, but then after a couple of minutes NetSaint starts not updating the
status.log file at all. With aggregate writes turned off, status.log
updating happens normally. But extremely often (3000 checks configured)

2) With the option of "-1" for external command read (i.e.: immediate read)
NetSaint runs off and consumes all available memory. After an hour or two
NetSaint has used up 3.5GB of swap and 900MB of real memory. With the read
interval set to positive values (1) this does not happen but the delay in
reading the external command pipe can sometimes be a significant length.

Anyone else noticed this behaviour? Ways to correct it?

Thanks

Jason

--
Jason Ahrens, System Analyst
TELUS Enterprise Solutions
http://www.telus.com




-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390