On 01/14/09 06:37, Edward Pilatowicz wrote: > imho, yes. > > if iftop has limitations wrt zones, i'd expect that to be documented. > (similar to how lack of ipv6 support is documented.) > > also, if this is the case i'd like to hear that improved support for > zones it being planned. (once again, similar to the ipv6 situation.) > Here is the update related solaris zones:
Now iftop has limitations with zones. iftop can not work properly in both shared stack zone and exclusive stack zone. Because it invokes DLPI functions. There are no resources available to add support at this time. I will work with the upstream community to provide full support for Solaris zones. > ed > > On Tue, Jan 13, 2009 at 03:53:46PM -0700, Jim Walker wrote: > >> Ed, >> >> We can provide this information. >> >> Just to clarify. Does any of this relate to the arc case? >> >> Cheers, >> Jim >> >> Here are the detail update on these questions: >> Edward Pilatowicz wrote: >> >>> i'd like to know how iftop interracts with zones. >>> >>> - can it be run inside of a zone (shared stack and/or exclusive stack)? >>> No. If it is compiled with HAVE_DLPI, it can not be run in both shared zone and exclusive zone because iftop report dlpi error inside zone. If it is compiled without HAVE_DLPI, it can run but not display any information of traffic on interfaces. >>> - if it runs inside of a zone, does it only display information for >>> interfaces present in that zone? >>> No. None traffic information is displayed. >>> - if run from the global zone, does it display information for all zones >>> on the system or just the global zone? >>> It display only the information in global zone if you do not specify the interface assigned to non-global zone. >>> - if run from the global zone, is there a way to display information for >>> just one specified zone? >>> Yes, from global zone, once you specify the interface assigned to the zone, it will display the traffic from/to the interface of the zone. It works for both shared zone and exclusive zone. Thanks for your comment. -- Best Regards, Xiang
