I've committed a memory error trap. Because this is a large change in impact (if small in # of lines), I've created a 2.1.56 and rolled the cvs version to 2.1.57pre. The 2.2 release plan stays intact, except that 2.1.57 -> 2.1.90. Look for the files on SourceForge shortly.
PLEASE test using .56 or .57pre (cvs) ONLY. The memory error trap allows the web server to stay up (maybe) after ntop runs out of memory - so we can get the info.html/textinfo.html report (and incidentally to save one last set of rrd data). Look for this in the log: ntop[9028]: ERROR: malloc(224) @ sessions.c:665 returned NULL [no more memory?] ntop[9028]: WARNING: ntop packet capture STOPPED. ntop[9028]: NOTE: ntop web server remains up. ntop[9028]: NOTE: Shutdown gracefully and restart with more memory. After an error occurs, all generated web pages (except the static ones such as help and man) will show "Packet capture stopped" at the top and bottom. Please record the log messages, the memory information from textinfo.html and sent it to the ntop-dev list. After that, just shutdown and restart. If the code causes problems, the run time parameter --disable-stopcap should revert to the old, broken, behavior. -----Burton _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
