Okay, I figured out a workaround.  I edited the ntop init script to use http
for port 3001 instead of https and it seems to be working much better. 
Perhaps you can put an option for http/https on the traffic monitoring page.

Thanks,
Chris
-- 
View this message in context: 
http://www.nabble.com/NTOP-unresponsive-high-CPU-utilization-tp23785167p23785847.html
Sent from the efw-user mailing list archive at Nabble.com.


------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
_______________________________________________
Efw-user mailing list
Efw-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/efw-user

Reply via email to