Ton Voon wrote:
This was fixed in the 3.1 branch, but we didn't do a release. We're
not doing any active development on 3.1 now. The 3.2 enterprise
version contains this fix and is due next week. The fix is also in
Opsview 3.3 (the next community version) which is due mid August.
OK no problem. I will make a note and upgrade at some stage when it gets
released.
Thanks again.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
