Glad I could help, will this be fixed in 2.0.4? Or is it already fixed
in the current codebase (git clone...)?
Thanks
John
Am 23.01.2013 00:50, schrieb Jean Raby:
On 13-01-18 1:41 PM, John Bieling wrote:
I investigated the problem further. I dumped the output of netstat
before and after I
On 23/01/13 03:18, John Bieling wrote:
Glad I could help, will this be fixed in 2.0.4? Or is it already fixed
in the current codebase (git clone...)?
It's fixed in git and will be part of 2.0.4.
--
Ludovic Marcotte
+1.514.755.3630 :: www.inverse.ca
Inverse inc. :: Leaders behind SOGo
On 13-01-18 1:41 PM, John Bieling wrote:
I investigated the problem further. I dumped the output of netstat
before and after I restarted sogo. Before the restart (running 12 h) I
had 280 conns (steadily increasing all day), after the restart I was
back to 40.
The diff shows that almost all of
I investigated the problem further. I dumped the output of netstat
before and after I restarted sogo. Before the restart (running 12 h) I
had 280 conns (steadily increasing all day), after the restart I was
back to 40.
The diff shows that almost all of the persistent connections, which only
My sogo installation is running on a virtuozo system (server4you.com)
and I have a limit of 1200 numtcpsock. If I sync my adressbook via
thunderbird, I can see via
cat /proc/user_beancounters
that the number of held numtcpsock is going up. But it is not going down
again, it just stays there.
