On 02/07/07, Peter Tribble <[EMAIL PROTECTED]> wrote: > On 7/2/07, Doug Scott <[EMAIL PROTECTED]> wrote: > > Alberto Ruiz wrote: > > > > > > 2007/7/2, Peter Tribble <[EMAIL PROTECTED] > > > <mailto:[EMAIL PROTECTED]>>: > > > > > > No, we should ship top and give users what they want. > > > > > > So, let's ship Microsoft Office with wine facilities. It's what the > > > people want ;-) > > Yes, but we don't have the rights to that :-( > > > Maybe you should actually give a good argument why top should not be > > shipped, rather than just try to argue for the sake of it. > > Arguing against 'top' is actually quite easy. i.e. prstat 'can' give > > more accurate information for less load on the system. Maybe the answer > > is to add an option to prstat to output 'top' like formatted data, and > > hardlink 'top' to prstat. > > Arguing why top should be shipped is quite easy, given the > relatively poor quality of prstat in many circumstances. (Not > all, I use prstat extensively too.) > > It shows the time, which means you can see at a glance how well > it's updating and at what interval. > > It shows the last pid, which shows you whether you've got a lot of > process creation going on, and the rough rate. > > It gives you a rough cpu summary (idle/user/kernel) > > It gives you a quick memory summary. > > You can not show idle processes, which can reduce the visual > clutter. > > You can select a user to show without exiting and restarting. > > You can sort without exiting and restating. > > You can change the update rate without exiting and restarting. > > You can zap an errant process directly from top without having > move to another window and type in something afresh. > > The TIME column is more readable. > > The CPU column has an extra decimal place. > > I prefer having LWP as a separate column - putting the process > name and number of LWPs together makes it harder to read. > > I find top output much more readable - I'm not sure why, but prstat > always seems more dense and cluttered. It may just be the order > of the columns and the spaces breaks it up a bit. > > As for resource utilization, that's pretty mixed. I would expect > top to be slightly heavier as it's displaying a wider range of > information, but sometimes find top to be lighter weight.
Those are all great reasons for shipping top. So, then the question becomes, should we fix prstat's shortcomings or ship top and accept defeat? (only half joking) This is a case where I would rather fix all the problems or shortcomings that prstat has then ship top simply because its easier. I would be inclined to fix prstat, and then setup a symlink so that when prstat is invoked as top, it shows output like top would... Do you foresee a problem with that? -- Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ "Beware of bugs in the above code; I have only proved it correct, not tried it. " --Donald Knuth _______________________________________________ indiana-discuss mailing list [email protected] http://opensolaris.org/mailman/listinfo/indiana-discuss
