HI all .. I've checked out all the docs and examples I can find .. but I can't seem to find the problem I'm having. I have a machine running samba 2.0.6 and I have a drive that I want to share. I have added the user I'm connecting with as a user in smbpasswd and I can connect the the server fine with username and password. I can also see my home dir and read/write to it fine .. I also have another share [install] comment = Install Directory path = /local/install public = yes writable = yes printable = no write list = @twilyt As you can see this is a public share with write access for group twilyt but it does not work.. I've made changes to the effect of this .. [install] comment = Install Directory path = /local/install valid users = hsmith public = no writable = yes printable = no write list = hsmith hsmith being the user that i connect with. I still cannot write to the share. am I missing something very badly ? The end result of what I need is a publicly shared drive read-only .. but writable for users in the group "twilyt" the group twilyt does contain hsmith in /etc/group Thanks Henti Smith Twilyt Productions http://www.twilyt.com
Is there anybody in the list who can tell me the influence of the oplock contention limit to control the locking behaviour on a shared directory/file? We have one file that is opened for write ops from several wkstations. It showed, that this file is being corrupted after some write ops. It has been told by the software manufacturer that they had under *some* conditions similar behaviour with a Novell server. They had to disable the write cache, there. Is it possible to slow the server so it behaves like a - sorry - weird Novell or NT box? Robert Robert Schott rschott@roottec.com ------------------------------------------
hentis@twilyt.com wrote:> > [install] > comment = Install Directory > path = /local/install > public = yes > writable = yes > printable = no > write list = @twilyt > > As you can see this is a public share with write > access for group twilyt but it does not work.. > > [install] > ..... > write list = hsmith > > hsmith being the user that i connect with. > > I still cannot write to the share.Check the logs to determine the actual user you are connected as. Also check the filesystem permissions to make sure that they will allow write access to that particular user. Cheers, jerry ---------------------------------------------------------------------- /\ Gerald (Jerry) Carter Professional Services \/ http://www.valinux.com/ VA Linux Systems gcarter@valinux.com http://www.samba.org/ SAMBA Team jerry@samba.org http://www.plainjoe.org/ jerry@plainjoe.org "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
ahhh!! obviously I found what I was searching for: oplock break wait time (G) This is a tuning parameter added due to bugs in both Windows 9x and WinNT. If Samba responds to a client too quickly when that client issues an SMB... but: DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE. My question, now: does it hurt to set from Default: oplock break wait time = 10 to 20 ms? anyone experimented, here?> Is there anybody in the list who can tell me the influence of the > oplock contention limit to control the locking behaviour on a shared > directory/file? > > We have one file that is opened for write ops from several wkstations. > It showed, that this file is being corrupted after some write ops. > > It has been told by the software manufacturer that they had under *some* > conditions similar behaviour with a Novell server. They had to disable the > write cache, there. > > Is it possible to slow the server so it behaves like a - sorry - weird > Novell or NT box? > > Robert
Thanks to all your guys :)) the problemwas rthe permissions on the filesystem .. I could not find any docs stating if I need to do that .. and assumed that samba will handle it ;p thanks again :) Henti Smith On Mon, Nov 27, 2000 at 09:29:03PM +0000, bruno patin wrote:> hi, > > have you verified the rigths on the unix directory ? we don't know if there is not any interdiction on it. > > hope that helps