Results 1 to 3 of 3
Thread: strange samba sharing problem
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Feb 2005
strange samba sharing problem
uname -a gives
Linux fc464 2.6.11-1.1369_FC4 #1 Thu Jun 2 22:56:33 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux
and smbd --version gives
[global] log file = /var/log/samba/%m.log load printers = yes guest account = guest idmap gid = 16777216-33554431 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 null passwords = yes username map = /etc/samba/smbusers encrypt passwords = yes public = yes winbind use default domain = no template shell = /bin/false dns proxy = no netbios name = fc64 cups options = raw writeable = yes server string = fcserver idmap uid = 16777216-33554431 workgroup = MYGROUP os level = 20 printcap name = /etc/printcap security = share create mode = 777 max log size = 50 directory mode = 777 [homes] comment = Home Directories browseable = no writeable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no printable = yes [share] browseable = no writeable = yes path = /share guest ok = yes comment = SHARE create mode = 777 directory mode = 777 available = no [carton] create mode = 777 path = /carton directory mode = 777 public = yes guest ok = yes writeable = yes [smb] path = /etc/samba
here's the story:
connect to samba as normal user, can go into carton share, but cannot write anything. copied a file into /carton (in linux) and it's shown from windwos machine. When tried to delete the file, windows gives no response (just like a file is deleted normally) but the file actually remains there. SELinux is disabled as well.....
any idea please??
When you copy the file using the linux filesystem, you wont attach the same permissions and ownership to it that you would from samba. Check the file permissions for what you copied in, and see if the person using samba has permissions to delete it.Linux user #126863 - see http://linuxcounter.net/
- Join Date
- Feb 2005
hi sorry and thanks for you reply
it turns out that my friend did not follow my instructions and turning selinux off actually solves the problem