Search |
Scout Module APISummary FileFile /proc/scout/accounts/summary provides an overview of usage per slice. An example: [princeton8@planetlab-3] cat /proc/scout/accounts/summary slice sent recvd sockcnt 735 2612 406 0 906 101173 769796 0 630 128152 31494 0 816 87215779 63074403 0 38 19952 14616 0 752 20715441 32329457 0 74 309936 210930 0 642 1156702 54851 1 900 2329907 6298539 7 28 14112 33401 0 99 1926602 14897404 5 0 1044464 15327866 7 unknown 5962227 2771272 0 The slice column identifies the slice, and the sent and recvd columns show how many bytes have been sent/received by the slice since the machine was booted. The sockcnt column shows how many sockets the slice currently has open. Loopback sockets are counted in the sockcnt column, but packets sent to the loopback address are not charged against the sent and recvd columns. The unknown slice ID is a catch-all category for packets that cannot be matched to a slice. An outgoing packet may be charged to unknown if it is sent by a socket not managed by the Scout module, for instance, one internal to the kernel (e.g, an ICMP socket that sends Echo Response packets) or one created during the boot process before the Scout module was loaded. Likewise, an incoming packet is charged to unknown if it does not demux to a socket managed by the Scout module. |
PlanetLab loginAnnouncements
|