Hullo,
I run a network of (amongst other things) FC5 desktops which connect to our fileserver using CIFS. The fileserver is running FC2 with smbd version 3.0.7-2.FC2, and we use pam_mount to mount per-user network shares on the desktops at login time. With the /etc/security/pam_mount.conf and /etc/pam.d/system-auth-ac files edited appropriately, this works fine on an unpatched FC5 install; however after a full yum update the directories won't allow reads:
$ ls /mnt/shares/share1 ls: /mnt/shares/share1: Operation not supported
Rolling back to the original kernel (i.e. from 2.6.18-1.2200.fc5 to 2.6.15-1.2054_FC5) makes the problem go away. I couldn't find any help for this by Googling around - is this a known issue?
The samba-client version is 3.0.23c-1.fc5.
Any help gratefully receieved,
Chris
Chris Linton-Ford wrote:
Hullo,
I run a network of (amongst other things) FC5 desktops which connect to our fileserver using CIFS. The fileserver is running FC2 with smbd version 3.0.7-2.FC2, and we use pam_mount to mount per-user network shares on the desktops at login time. With the /etc/security/pam_mount.conf and /etc/pam.d/system-auth-ac files edited appropriately, this works fine on an unpatched FC5 install; however after a full yum update the directories won't allow reads:
$ ls /mnt/shares/share1 ls: /mnt/shares/share1: Operation not supported
Rolling back to the original kernel (i.e. from 2.6.18-1.2200.fc5 to 2.6.15-1.2054_FC5) makes the problem go away. I couldn't find any help for this by Googling around - is this a known issue?
The samba-client version is 3.0.23c-1.fc5.
Any help gratefully receieved,
Chris
This is a known issue. Check out this bugzulla.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211070
Akemi
On Fri, 3 Nov 2006, A Yagi wrote:
Chris Linton-Ford wrote:
This is a known issue. Check out this bugzulla.
I believe there is a test kernel in the process of appearing in the updates-testing repository that should address this according to the change log (the kernel was announced on the fedora-test mailing list a couple of hours ago).
Michael Young
On Fri, 2006-11-03 at 17:06 +0000, M A Young wrote:
On Fri, 3 Nov 2006, A Yagi wrote:
Chris Linton-Ford wrote:
This is a known issue. Check out this bugzulla.
I believe there is a test kernel in the process of appearing in the updates-testing repository that should address this according to the change log (the kernel was announced on the fedora-test mailing list a couple of hours ago).
Michael Young
Thanks for this - I'll hold updates until the new kernel comes out.
Cheers,
Chris