2012-12-05T16:40:55ZFluxBBhttps://bbs.archlinux.org/viewtopic.php?id=154128I figured it out, there was not space left on my root (/) device. After cleaning pacman cache everything works like it should ]]>https://bbs.archlinux.org/profile.php?id=191222012-12-05T16:40:55Zhttps://bbs.archlinux.org/viewtopic.php?pid=1202262#p1202262That doesn't solve the original problem ]]>https://bbs.archlinux.org/profile.php?id=191222012-12-05T16:23:46Zhttps://bbs.archlinux.org/viewtopic.php?pid=1202256#p1202256read only = yes ??]]>https://bbs.archlinux.org/profile.php?id=104632012-12-05T14:51:54Zhttps://bbs.archlinux.org/viewtopic.php?pid=1202208#p1202208I don't want the files to be writable. I need the users to be able to read the files, but not write.]]>https://bbs.archlinux.org/profile.php?id=191222012-12-05T14:01:27Zhttps://bbs.archlinux.org/viewtopic.php?pid=1202189#p1202189Maybe you need to set writeable = yes in your smb.conf?]]>https://bbs.archlinux.org/profile.php?id=104632012-12-05T13:54:45Zhttps://bbs.archlinux.org/viewtopic.php?pid=1202187#p1202187As the title says, my windows clients can browse samba files but can't access them (open or copy).
This bug appeared as a result of some recent update, but I don't know which one (it's not samba).