Aníbal Monsalve Salazar wrote:
On Wed, Aug 27, 2008 at 10:50:31AM +0200, Vincent Danjean wrote:
But I would like to know if you recommend adding this option on all
clients or if you will think it will be solved (in the kernel or in
nfs-common) before this bugs reaches testing (was it for lenny
Hi,
I experiment the same problem in my lab which has an etch nfs server.
When stations are upgraded to nfs-common 1:1.1.3-1, users cannot access
their files. Adding sec=sys to the client's mount options fix the problem.
As I found the fix in Debian bug report, I did not make yet another
Aníbal Monsalve Salazar [EMAIL PROTECTED] writes:
The basic symptom was that it acted as if I was a different user: I
could not access my files unless they were world-readable.
Please try the workaround found by Paul Collins (add sec=sys to the
client's mount options) and tell us if it fixed
On Wed, Aug 27, 2008 at 10:50:31AM +0200, Vincent Danjean wrote:
But I would like to know if you recommend adding this option on all
clients or if you will think it will be solved (in the kernel or in
nfs-common) before this bugs reaches testing (was it for lenny or
lenny+1)
This bug is not in
On Mon, Aug 04, 2008 at 12:37:19AM +1200, Paul Collins wrote:
I discovered today that I was no longer able to write to the v3 mount
on my 1.1.2 server. I checked /proc/mounts and noticed sec=null on the
mount. Either adding sec=sys to the client's mount options or
downgrading to nfs-common 1.1.2
Package: nfs-common
Version: 1:1.1.3-1
Severity: important
After upgrading from nfs-common 1:1.1.2-6 to 1:1.1.3-1, some nfs-mounted
filesystems became almost unusable.
The basic symptom was that it acted as if I was a different user: I
could not access my files unless they were
6 matches
Mail list logo
