Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262001AbUJYQAN (ORCPT ); Mon, 25 Oct 2004 12:00:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262031AbUJYQAB (ORCPT ); Mon, 25 Oct 2004 12:00:01 -0400 Received: from linux01.gwdg.de ([134.76.13.21]:41964 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S262008AbUJYPrK (ORCPT ); Mon, 25 Oct 2004 11:47:10 -0400 Date: Mon, 25 Oct 2004 17:46:52 +0200 (MEST) From: Jan Engelhardt To: Denis Vlasenko cc: Trond Myklebust , linux-kernel@vger.kernel.org Subject: Re: Temporary NFS problem when rpciod is SIGKILLed In-Reply-To: <200410251831.10849.vda@port.imtp.ilyichevsk.odessa.ua> Message-ID: References: <200410251702.58622.vda@port.imtp.ilyichevsk.odessa.ua> <200410251812.28663.vda@port.imtp.ilyichevsk.odessa.ua> <200410251831.10849.vda@port.imtp.ilyichevsk.odessa.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=koi8-r Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 611 Lines: 17 >It is not killable, neither 2.4 nor 2.6 one. It is by design I think, >because I *must not* kill it, or else NFS rootfs will fall off >and box will hang. If it's not killable (per kill(2)), why can killall5 (which will probably use kill(2)!) do it? Jan Engelhardt -- Gesellschaft f?r Wissenschaftliche Datenverarbeitung Am Fassberg, 37077 G?ttingen, www.gwdg.de - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/