From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Moy4o-0000ax-4S for garchives@archives.gentoo.org; Sat, 19 Sep 2009 11:26:02 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0BE78E072B; Sat, 19 Sep 2009 11:26:01 +0000 (UTC) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by pigeon.gentoo.org (Postfix) with SMTP id 80AF9E072B for ; Sat, 19 Sep 2009 11:26:00 +0000 (UTC) Received: (qmail invoked by alias); 19 Sep 2009 11:25:59 -0000 Received: from p54851947.dip0.t-ipconnect.de (EHLO gmx.net) [84.133.25.71] by mail.gmx.net (mp046) with SMTP; 19 Sep 2009 13:25:59 +0200 X-Authenticated: #20088476 X-Provags-ID: V01U2FsdGVkX1/QKeVEkuPQWXP5A/hDzc1jW0XHu5zT2pUNbipb9A kocMUv+SfZaSVs Received: by gmx.net (nbSMTP-1.00) for uid 1001 Meino.Cramer@gmx.de; Sat, 19 Sep 2009 13:26:00 +0200 (CEST) Date: Sat, 19 Sep 2009 13:25:59 +0200 From: meino.cramer@gmx.de To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Shutting down process hangs - how to proceed? Message-ID: <20090919112559.GA27909@solfire> References: <20090919013959.GA5295@solfire> <4AB43A71.5080805@gmail.com> <20090919020840.GB5295@solfire> <200909191028.14764.michaelkintzios@gmail.com> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: mutt-ng/devel-r804 (Linux) X-Y-GMX-Trusted: 0 X-FuHaFi: 0.75 X-Archives-Salt: 38f53fa3-27d1-498b-a3f1-9ed7f7a77f34 X-Archives-Hash: ae2913008e3b560030b71d00310b3069 > Hi, > I got a similar problem too once... and what was making the system > hang wasn't the last shutting down thing listed, but the one just > after (so i don't think it's net.lo fault in your case). So i suggest > to have a look at which services are started at boot, but aren't > shutted down. Turning off parallel boot could help you find out the > responsible service. > In my case it was a misconfiguration of the alsa module, which > shouldn't be unloaded at shotdown time... > HTH > Davide Hi Davide, Is there any way to figure out, in which sequence what is shut down *without* actually shutting down ther system? Have a nice weekend! :) Best regards, mcc -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.