On Jan 4, 2008 3:48 AM, Alexander Welter <[EMAIL PROTECTED]> wrote: > > The normal problem with gathering system utilization data is, that > we're talking about productive systems. Installing tools and running > them in a root context on a productive system would be a change in > the system and that's somthing most customers don't like at all. It > requires a change request, evaluation and an approval, which will > take *some* time.
Does this help? $ ps -o uid -p $$ UID 535 $ kstat -p :::opackets64 :::ipackets64 5 eri:0:eri0:opackets64 260853430 eri:0:eri0:ipackets64 266455748 eri:0:eri0:opackets64 260853464 eri:0:eri0:ipackets64 266455828 eri:0:eri0:opackets64 260853476 eri:0:eri0:ipackets64 266455880 ^C kstat(1M) can give you quite a bit of other information as well. It is implemented as a perl script, so if the output isn't exactly as you need it (e.g. you need deltas not absolute values) it wouldn't be terribly hard to implement. -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
