That's dependent on whether the OS presents it to the program in the scan... since it's USB and thus dynamic, almost certainly it will not be seen by nTop. nTop does not go back and re-scan at anytime (unless the source has significantly changed in that area in the last 5 years).
So add a dependency to your startup scripts to bring the network up first, then nTop. That's always a good idea - if you start nTop before the network is up there's nothing to see here. -----Burton %QUOTE% -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Robbie Smith Sent: Sunday, November 20, 2011 3:42 AM To: [email protected] Subject: [Ntop] Running ntop as daemon Hello everyone I just have a quick question: I'm trying to monitor my net usage on a single local machine, and at the moment my primary interface is a USB ppp modem, so I normally don't bring the interface up until after I've logged in. If I include ntop in my system daemon list (I'm running Arch Linux), what is its expected behaviour if an interface is unavailable? Will it exit or crash, or wait for the interface to become available? Also, can I monitor multiple interfaces at once, for example, ppp0 and wlan0? Robbie _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
