From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KM8Gs-00080F-KP for garchives@archives.gentoo.org; Thu, 24 Jul 2008 21:22:46 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9A60CE04D3; Thu, 24 Jul 2008 21:22:44 +0000 (UTC) Received: from aa011msr.fastwebnet.it (aa011msr.fastwebnet.it [85.18.95.71]) by pigeon.gentoo.org (Postfix) with ESMTP id 06F73E04D3 for ; Thu, 24 Jul 2008 21:22:44 +0000 (UTC) Received: from [37.1.3.90] (37.1.3.90) by aa011msr.fastwebnet.it (8.0.013.5) (authenticated as cyclopia) id 4887884700386867 for gentoo-user@lists.gentoo.org; Thu, 24 Jul 2008 23:22:43 +0200 Message-ID: <4888F490.6060108@gmail.com> Date: Thu, 24 Jul 2008 23:30:56 +0200 From: "b.n." User-Agent: Thunderbird 2.0.0.14 (X11/20080507) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] ps command References: <6b16fb4c0807230109m3082f32p140648211f7cdae9@mail.gmail.com> <48885C6D.3020103@gmail.com> <200807241709.44433.alan.mckinnon@gmail.com> <200807241732.10353.shrdlu@unlimitedmail.org> In-Reply-To: <200807241732.10353.shrdlu@unlimitedmail.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: a400ddfd-7bd1-4089-ac93-0ff2a5754601 X-Archives-Hash: 8ec0076d542197e580da7ff7b30a1f44 Etaoin Shrdlu ha scritto: > From what I know, "blocked" is the same as "sleeping", ie waiting for > something to happen. Tasks that have completed their time slice and are > forced by the scheduler to stop, are not "sleeping"; they are > re-inserted in the queue of the runnable processes, and the scheduler > picks them up again from there when another time slice is assigned to > them. These processes are in the "runnable" or "ready" state. > > But of course I may be wrong, so corrections welcome. Thanks, the wikipedia article is very clear. m.