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: <4AE9430B.3060105@suse.de>
Date:	Thu, 29 Oct 2009 12:53:55 +0530
From:	Suresh Jayaraman <sjayaraman@...e.de>
To:	Yinghai Lu <yhlu.kernel@...il.com>
CC:	David Miller <davem@...emloft.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	NetDev <netdev@...r.kernel.org>
Subject: Re: nfs broken in net-next?

On 10/29/2009 01:43 AM, Yinghai Lu wrote:
> pk12-3214-189-102:~ # mount -t nfs 10.6.75.100:/data/shared/pxeboot /x
> mount.nfs: rpc.statd is not running but is required for remote locking.
> mount.nfs: Either use '-o nolock' to keep locks local, or start statd.

rpc.statd on client should have be started by mount.nfs when a nfs
filesystem is mounted. Is this not happening for some reason or do you
see any errors in syslog?

> 
> using opensuse11.1
> 

Are you using 11.1 betas? I know of a problem where non-root user mounts
fail to start rpc.statd in betas that got fixed later:

http://marc.info/?l=linux-nfs&m=122748525624094&w=2

Is the problem seen only recently (after updating to net-next)?

Thanks,

-- 
Suresh Jayaraman
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ