linux-kernel - Re: in-kernel rpc.statd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1GJzw4-0002ti-00@calista.eckenfels.net>
Date:	Sun, 03 Sep 2006 23:55:24 +0200
From:	Bernd Eckenfels <ecki@...a.inka.de>
To:	linux-kernel@...r.kernel.org
Subject: Re: in-kernel rpc.statd

In article <Pine.LNX.4.61.0609032255010.6844@...hk01.tjqt.qr> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/