Permission and odd behaviour (RFH)

[Guinness2702]

Hi, can anybody help me with the following please:-

I've have just migrated to a new server (old FC5, new FC6). I have migrated my samba config from the old box.

As far as I can see, the config is correct (I hardly changed anything), but samba logs a "/mnt/share" permission denied error when I try to connect.
When I changed the path of the share to "/tmp/share" it worked. The permissions/ownership of the directories are all identical, and yet it works with one and not the other.
The other strange behaviour I noticed is that although I could copy a file from the client to the tmp share, the client could not see any of the files I manually added (on the server) to the share. Even if I rebooted both client and server (and indeed connected from a different client), only the file I had copied to the share from a client was visible. I renamed the file on the server, and the client picked up this change. (/mnt/share) is just a different ext3 partition mount point, and my non-root user can access it on the server so I don't believe there is a problem with the mount parameters - default).

Has anybody seen this behaviour before, or can anybody give me a pointer as to what I might need to do to get it working?

Thanks,
Steve

 

[PHV]

Without seeing your samba.conf file, it's hard to say anything ...

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[Guinness2702]

[global]
workgroup = MSHOME
hosts allow = 192.168.0.
security = user
interfaces = eth1
preferred master = yes
dns proxy = no
[homes]
comment = Home Directories
browseable = no
writable = yes

[data]
comment = data directory
path = /mnt/share
writable = yes
public = no

[tmp]
comment = tmp directory
path = /tmp/share
writable = yes
public = no

This is everything that is not a comment. The only change from the previous install is that interfaces was eth0 and is now eth1, and that the filesystem on /mnt/share is ext3 whereas the old was ext2

[2006/12/02 04:42:26, 0] smbd/service.c:make_connection_snum(911)
'/mnt/share' does not exist or permission denied when connecting to [data] Error was Permission denied

[yyy@xxx ~]$ ls -latrd /mnt/share
drwxrwxrwx 3 root root 4096 Dec 2 02:57 /mnt/share
[yyy@xxx ~]$ ls -latrd /tmp/share
drwxrwxrwx 2 root root 4096 Dec 2 05:12 /tmp/share

 

[PHV]

What is the output of this command ?
ls -lad /mnt

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[Guinness2702]

[root@yyy ~]# ls -lad /mnt/
drwxrwxrwx 5 root root 4096 Dec 2 00:39 /mnt/

Like I said, I think the permissions are correct. My ordinary user (same one I am logging in to samba as) can access the filesystem from the server, just not remotely, via samba. :\

 

[Guinness2702]

Right, I've got it sussed after a bit more testing and a bit more web searching, the problem is something called SELinux, which comes with FC6, which seems to interfere with samba somehow (some additional security stuff at the kernel level from what i can figure). To fix, I just disabled it (although you could probably play with it's settings too - it's on the system/administration menu under security settings)

For the benefit of people who STFW for the same problem, keywords: samba, fedora core 6, missing files, invisible files, file permissions