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] [day] [month] [year] [list]

Message-ID: <20060904080924.GA23460@pc51072.physik.uni-regensburg.de>
Date:	Mon, 4 Sep 2006 10:09:24 +0200
From:	Christian Guggenberger 
	<christian.guggenberger@...sik.uni-regensburg.de>
To:	Trond Myklebust <trond.myklebust@....uio.no>
Cc:	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Christian Guggenberger 
	<christian.guggenberger@...sik.uni-regensburg.de>,
	linux-kernel@...r.kernel.org
Subject: Re: in-kernel rpc.statd

> > 
> > 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?
> 
> Yes. Locking over NFSv2/v3 won't work without it.
> 
> That said, there is no reason why we need an rpc.statd in the kernel
> when the nfs-utils package already provides one that works fine in
> userland.
>

I know. The reason behind my query was just that Suse distros - SLES9 at
least - do not provide userland rpc.statd anymore.

cheers.
 - Christian

-- 
VGER BF report: H 3.23172e-09
-
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/