Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261933AbUJYP1p (ORCPT ); Mon, 25 Oct 2004 11:27:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261950AbUJYPYp (ORCPT ); Mon, 25 Oct 2004 11:24:45 -0400 Received: from linux01.gwdg.de ([134.76.13.21]:22250 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S261933AbUJYPUp (ORCPT ); Mon, 25 Oct 2004 11:20:45 -0400 Date: Mon, 25 Oct 2004 17:20:30 +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: <200410251812.28663.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> 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: 745 Lines: 22 >That's the point. It works in 2.4 Maybe because there is no rpciod in 2.4? >Well, let's see. 2.4 works. rpciod in 2.6 shows this erratic behaviour >even if I do "kill -9 ", thus no other process, kernel >or userspace, know about this KILL. Is rpciod (a kthread as I read from your 'ps' output) killable in 2.4 after all? Maybe the rpciod-26 is missing a sigblock()? 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/