From: Afanasov Dmitry <ender@atrus.ru>
To: community@altlinux.ru
Subject: Re: [Comm] Re: process vs thread list (was: Re: amarok using troubles)
Date: Fri, 25 Mar 2005 00:53:07 +0300
Message-ID: <20050324215307.GC10082@nick.comp-mir.ru> (raw)
In-Reply-To: <20050324212027.GN8616@osdn.org.ua>
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
On Thu, Mar 24, 2005 at 11:20:27PM +0200, Michael Shigorin wrote:
> On Fri, Mar 25, 2005 at 12:12:38AM +0300, Afanasov Dmitry wrote:
> > кстати, когда-то под 2.4 я заметил, что по top и ps треды не
> > были видны - как-то по другому можно было выдрать. как это
> > можно вернуть? или мне показалось? :) тогда в любом случае -
> > как сделать, чтоб по умолчанию показывались только процессы в
> > htop, top, ps и иже с ними?
>
> Уй... я в этой фичепляске с procps и ядром не то что бы совсем
> запутался, но отслеживать определённо лень. Благо оба варианта
> поведения вполне устраивают. :)
>
> Погуглите "procps top threads", скорее всего отыщется.
хмы, даже нашёл:
Why do ps and top show threads individually?
The 2.4.xx kernel does not provide proper support for grouping threads by
process. Hacks exist to group them anyway, but such hacks will falsely
group similar tasks and will fail to group tasks due to race conditions.
The hacks are also slow. As none of this is acceptable in a critical
system tool, task grouping is not currently available for the 2.4.xx
kernel. The 2.6.xx kernel allows for proper thread grouping and reporting.
To take advantage of this, your programs must use a threading library that
features the CLONE_THREAD flag. The NPTL pthreads provided by recent glibc
releases use CLONE_THREAD.
вот и ответ. может не затеряется в рассылке, а кто-то с переводом добавит
в faq? :)
--
С уважением,
Афанасов Дмитрий
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-24 21:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 20:10 [Comm] amarok using troubles Afanasov Dmitry
2005-03-24 20:38 ` Gray_graff
2005-03-24 21:09 ` Afanasov Dmitry
2005-03-25 6:38 ` Stanislav Yadykin
2005-03-24 20:49 ` [Comm] " Michael Shigorin
2005-03-24 21:12 ` [Comm] process vs thread list (was: Re: amarok using troubles) Afanasov Dmitry
2005-03-24 21:20 ` [Comm] " Michael Shigorin
2005-03-24 21:53 ` Afanasov Dmitry [this message]
2005-03-24 22:03 ` [Comm] [vsu, ldv?] " Michael Shigorin
2005-03-24 21:48 ` [Comm] amarok using troubles Vasily Kolomeets
2005-03-24 22:08 ` Afanasov Dmitry
2005-03-24 23:48 ` Vasily Kolomeets
2005-03-25 6:41 ` Afanasov Dmitry
2005-03-26 1:06 ` [Comm] " Arioch
2005-03-26 13:10 ` [JT] Re: [Comm] " php-coder
2005-03-25 6:35 ` Stanislav Yadykin
2005-03-25 6:57 ` Afanasov Dmitry
2005-03-25 9:39 ` Stanislav Yadykin
2005-03-25 11:25 ` Afanasov Dmitry
2005-03-25 11:47 ` Stanislav Yadykin
2005-03-25 12:09 ` Afanasov Dmitry
2005-03-25 7:23 ` Afanasov Dmitry
2005-03-25 9:42 ` Stanislav Yadykin
2005-03-25 11:32 ` Afanasov Dmitry
2005-03-25 11:49 ` Stanislav Yadykin
2005-03-25 13:25 ` Afanasov Dmitry
2005-03-25 14:16 ` Vasily Kolomeets
2005-03-25 14:49 ` Afanasov Dmitry
2005-03-25 14:59 ` Stanislav Yadykin
2005-03-28 6:17 ` Afanasov Dmitry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050324215307.GC10082@nick.comp-mir.ru \
--to=ender@atrus.ru \
--cc=community@altlinux.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Community general discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
public-inbox-index community
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.community
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git