On Mar 7, 2011, at 13:01, Zack Perry wrote: > I downloaded your port, and tested it side by side with my own build. Their > behavior is the same. Two visible differences: > > • Neither are quick in responding to network events as their > counterpart running on Linux (e.g. CentOS 5.5 and Ubuntu 10.04, both I use > active. On Linux, even a ping to a remote host (e.g. www.google.com) > generates visible node cicles and traffic graphs in Etherape, not on OS X. > Although in the Prot. pane, traffic stats are updated periodically as > anticipated > • Even significant network traffic (e.g. downloading OpenOffice dmg > file from http://www.openoffice.org/) doesn't generate visible node cicles > and traffic graphs in the Etherape running in OS X. In Linux, the entire > display probably would be filled completely by such an event. > > I am not sure why there are such "behavior" differences. The lack of visible > traffic graphs and node cicles make Etherape much less useful in OS X IMHO. > > BTW, I did try etherape from both Fink and MacPorts, but due to the less > comprehensive coverage of Fink, I favor MacPorts more. I have done a > > chmod 0 /sw/bin/dbus-daemon > > and removed /sw/bin from my $PATH, so I should be using exclusively MacPorts > now. But issues with Etherape has been quite puzzling to me. Further > hints/suggestions as to how to rectify Etherape's behavior are appreciated.
I'm afraid I've never used etherape and don't know anything about it; you might want to try asking the developers of the software. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
