Hi all, the plugin (de)activation problem should be fixed. This is the cause:
- it's some time I'm playing with fork(): ntop is now forked (as Apache for instance) when a new HTTP request is received - all the operations that modify ntop's behaviour should *not* be performed inside the child process - the plugin (de)activation was performed in the child process: this was the problem Does somebody has experienced problems with fork(). Is ntop creating zombies? Nobody reported me problems: shall i assume that everything is working well (am I too optimistic?)? Cheers, Luca -- Luca Deri NETikos S.p.A. Via Matteucci 34/B 56124 Pisa, Italy. Ph. +39/050/968.639 Fax. +39/050/968.626 Personal: [EMAIL PROTECTED] Business: [EMAIL PROTECTED] WWW: http://www.lucaderi.org/ ICQ: 68183632 Hacker: someone who loves to program and enjoys being clever about it - Richard Stallman _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listmanager.unipi.it/mailman/listinfo/ntop
