Well, that's 1) not what I asked for 2) not going to help debugging ntop 3) an unsupported development version - IIRC sFlow was added after 2.1.3
You might try talking to InMon, as they provided the code originally. AFAIK, sFlow wasn't heavily tested during the development cycle (nobody that I remember reported using it). Anyway, without your effort at tracking this down, I'm going to drop the PR_ -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Scott Stone Sent: Tuesday, June 03, 2003 6:49 PM To: [EMAIL PROTECTED] Subject: Re: [Ntop] not closing correctly/saving plugin config state sFlow plugin (PR_PYR6EVB) I actually had to back out to version 2.1.x - i notice that after a period of about 30-60 minutes, 2.2 will just *hang* and i have to sig9 it to stop it at all... very irritating... the SFLOW stuff seems to work pretty well, when ntop itself is behaving properly. --- "Burton M. Strauss III" <[EMAIL PROTECTED]> wrote: <snip /> > Post the startup messages from the log. > > When you make the changes, re-enter the plugins page (knock down the > browser, restart it, admin | plugins) and see if there's a red > message on > sFlow, or if it's listed then as active (could be a cached page, > although > that piece isn't supposed to, some proxies think they're smarter than > the > instructions in the html text). > > There's not been a lot of feedback about sFlow, so I'm not aware of > any > users out there... gang? > > > -----Burton _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
