Date: Fri, 13 May 2005 08:27:50 -0400 (EDT) From: Andre Guibert de Bruet <andy@siliconlandmark.com> To: Giorgos Keramidas <keramida@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Strange top(1) output Message-ID: <20050513082431.D820@lexi.siliconlandmark.com> In-Reply-To: <20050513113151.GD934@orion.daedalusnetworks.priv> References: <cswiger@mac.com> <E1DWDNe-0005AE-3p@cs1.cs.huji.ac.il> <20050512.220006.124086156.imp@bsdimp.com> <42847665.4030803@mac.com> <20050513102116.GD9642@orion.daedalusnetworks.priv> <42848CD4.50501@mac.com> <20050513113151.GD934@orion.daedalusnetworks.priv>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 13 May 2005, Giorgos Keramidas wrote: > On 2005-05-13 07:17, Chuck Swiger <cswiger@mac.com> wrote: >> Giorgos Keramidas wrote: >>> The format of our top, to make comparisons easier is: >>> 1 2 3 4 5 6 7 8 >>> 12345678901234567890123456789012345678901234567890123456789012345678901234567890 >>> +-------------------------------------------------------------------------------- >>> | PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND >>> |54842 root 1 8 0 2364K 1884K wait 0:09 10.91% 10.69% sh >>> | 762 keramida 1 96 0 82432K 31280K select 4:53 0.00% 0.00% Xorg >>> |65426 keramida 4 20 0 44240K 34152K kserel 4:12 0.00% 0.00% firefox-b >>> | 814 keramida 1 96 0 6188K 4424K select 1:06 0.00% 0.00% wmaker >> >> There's four blanks there, so one could handle usernames up to 11 >> characters long. Or else remove the double-space between USERNAME and THR. > > It's not a bdouble space. The THR column has a width of 4 characters > and a title of 3; that's why it looks like a double space :-$ On Solaris, the THR column is 3 characters wide. I think that everyone would be happy to see an extra column for the COMMAND field. :-) >> Agreed. The question to answer, is how should one display the busiest >> threads of a process usefully in the top display? Figuring that one >> out would be useful to answering other questions about what top should >> look like. > > In "thread mode", every thread gets its own line. In that case, you get > what you're looking for. It's just not the default display mode, but > it's easily enabled by hitting 'H'. > >>> Unfortunately, the current top uses very few of the features that a full >>> blown curses implementation would have. >> >> Curses by slow accumulation, rather than curses by design? Ick. :-) > > Bingo :) Yikes! Andy /* Andre Guibert de Bruet * 6f43 6564 7020 656f 2e74 4220 7469 6a20 */ /* Code poet / Sysadmin * 636f 656b 2e79 5320 7379 6461 696d 2e6e */ /* GSM: +1 734 846 8758 * 5520 494e 2058 6c73 7565 6874 002e 0000 */ /* WWW: siliconlandmark.com * Tormenting bytes since 1980. */
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050513082431.D820>