From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 06F2A138CC5 for ; Sun, 22 Mar 2015 12:04:50 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 975E5E08B5; Sun, 22 Mar 2015 12:04:44 +0000 (UTC) Received: from mail-ig0-f176.google.com (mail-ig0-f176.google.com [209.85.213.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 91C7CE0895 for ; Sun, 22 Mar 2015 12:04:43 +0000 (UTC) Received: by igcau2 with SMTP id au2so21465442igc.0 for ; Sun, 22 Mar 2015 05:04:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=+iQ3VgjI3oI757mTyL6AjeaGxegPmvcGd57A4wtPGpA=; b=J6QdO+X46mi+3uIHyxXo7KgPokIHv0qfxyFR4eUigW30piO8J6LcG7mtZLR38LwhtP T+JF7JHcJrWSSffiORka74bVmvxyhNOHe8D27hkBOoagu0F5vdYgpkEDdcr2YwKRvI9e gfo0erCG6aCISs+o5ry0GRHwC+Cwgza4/znDYoyd1LKSVfKr5YVvRvlK9nrayL4Hg3d8 B37O2Ig3kVSOJNehUWqQ5g3Y5b7Z60ElNy1askI2V+mi/DbqSzEaZx/gnx6BMNkVywzo LfI3QjuFjY0rRg5cHjP780qOMc73afWIkpC2tf1/NXu9F672omxKTMgWizbnhPYtVa40 v3wQ== 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 X-Received: by 10.50.254.4 with SMTP id ae4mr8053853igd.10.1427025882864; Sun, 22 Mar 2015 05:04:42 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.107.135.78 with HTTP; Sun, 22 Mar 2015 05:04:42 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Mar 2015 08:04:42 -0400 X-Google-Sender-Auth: TwSNNTlBYG6P6Sx87FietDNcv1s Message-ID: Subject: Re: [gentoo-user] systemd: incorrect behavior when doing poweroff/reboot From: Rich Freeman To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: cd267b49-4060-4a36-a3a2-2e526399411b X-Archives-Hash: 15e985e59b6dd9d5a3dfae232b87451c On Sat, Mar 21, 2015 at 6:44 PM, walt wrote: > I'd be 100% sure this is a systemd bug except that the problem is so > obvious and (I think) so common that I can't believe I'm the only > systemd user seeing it: > > I routinely share /usr/portage over NFS between several gentoo boxes > on my wireless network. When I poweroff or reboot the NFS client > machines, systemd tears down the wireless connection *before* it > unmounts the /usr/portage share, and so the umount command hangs and > the machine won't shut down. > > I'd think people that hang out in this list must do the same thing, > surely? No one else here running into this silly problem? > Log a bug. systemd is very new, and if you have a somewhat-unusual configuration (nfs over wifi, for example) it is entirely possible that nobody has noticed a bug like this. I was having issues with an nfs root with dracut+systemd and I found the maintainers of both very interested in bug reports and testing. It seems likely that a dependency is unspecified somewhere. As far as whether the bug is in systemd or dracut, if you have systemd enabled on dracut then dracut will be running systemd anyway, so the config issue will get you either way. -- Rich