Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750758AbWICVz2 (ORCPT ); Sun, 3 Sep 2006 17:55:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750804AbWICVz2 (ORCPT ); Sun, 3 Sep 2006 17:55:28 -0400 Received: from quechua.inka.de ([193.197.184.2]:7838 "EHLO mail.inka.de") by vger.kernel.org with ESMTP id S1750758AbWICVz1 (ORCPT ); Sun, 3 Sep 2006 17:55:27 -0400 From: Bernd Eckenfels To: linux-kernel@vger.kernel.org Subject: Re: in-kernel rpc.statd Organization: Private Site running Debian GNU/Linux In-Reply-To: X-Newsgroups: ka.lists.linux.kernel User-Agent: tin/1.7.8-20050315 ("Scalpay") (UNIX) (Linux/2.6.13.4 (i686)) Message-Id: Date: Sun, 03 Sep 2006 23:55:24 +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 691 Lines: 19 In article you wrote: > Hm. I do not have a rpc.statd userspace program nor kernel daemon (running > on 2.6.17-vanilla). Yet everything is working. Is there a specific need for > statd? It is more or less an uptime notification protocol for NFS locks. I think NFS clients can recover from a reboot without the help of the statd in most situations. Gruss Bernd -- VGER BF report: H 0.429236 - 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/