On Fri, Jun 13, 2008 at 11:39 AM, Gary Gatten <[EMAIL PROTECTED]> wrote: > Syslog output to start. Try starting nTop with -t 5 or 6 and -K. If > syslog has no benefits you'll have to run in the debugger to capture the > crash in more detail. > > G
I just posted a fragment of syslog output - is that sufficient? I've kicked up -t from 4 to 6, but already had -K. Here are the flags from /etc/rc.conf, after editing: ntop_flags="-d -u ntop -P /home/ntop/databases -K -L -t 6 -o -i fxp0 -m 192.168.8.0/24,192.168.9.0/24,192.168.10.0/24,192.168.11.0/24,192.168.12.0/24,192.168.13.0/24,192.168.15.0/24,192.168.24.0/24 -w 192.168.24.239:3000 -W 0 -D mycompany.com" Kurt _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
