On 21/09/10 7:47 AM, Anton Popov wrote:
Nothing other than what I have already sent.
sogo logs seem normal otherwise, it is very possible that the lack of
memory caused this "safety belt" and was caused by something else.
I only ask this question because this has never happened before and
started right after I upgraded to the nightly and I thought both may
be connected, plus I was running "top" yesterday I saw sogod on the
top of the memory usage list but I did not think much of it and did
not notice the actual usage, just remember it was on top when I sorted
by memory usage.
I will keep monitoring the system and will let you know.
No problem, thanks.
How was the upgrade to the nightly builds as you have a large iCal 3 / 4
user base?
Regards,
--
Ludovic Marcotte
[email protected] :: +1.514.755.3630 :: www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
--
[email protected]
https://inverse.ca/sogo/lists
