I installed SUSE 10 for a client that required basic file sharing over their p2p network. Everything runs smoothly except one application they run will not let other users in if another user has saved a file. I found that when the ownership of these files is set to 'root' there are no problems, but as soon as a user in the group saves again they take ownership and hence the problem occurs again. They all need access and the ability to save these files. It is a multi-user app that worked fine accessing shares on a XP box. My question is this, how can I setup the group so that they can save files without taking ownership and if that's not an option how can I change the files so that they can save without ownership. I have setup *NIX stations in the past, but have never needed or had the time to become real familiar with the OSs' so I would consider myself a newbie. That said, please keep answers relatively simple . Thx.

Since there haven't been any responses, I should probably clarify a little more. The users all run Windows XP SP2. They run a program called Simply Accounting that accesses a share over the network that is on the SUSE 10 machine running Samba. They all have identical drive mappings to the share. Everything runs fine until someone saves changes made to a file thereby taking ownership of the file on the Samba share. This excludes anyone from viewing, logging into Simply or making any changes to the files until I manually change the owner back to root and apply permissions for the group. Are there any permissions I need to change on the Windows side of things?

We had a similar problem.
Our soultion was to use the "force user" paramter to force samba to keep all files in the share owned by the same single user, regardless of who accesses the share.

You may also need the "force create mode" but we have not yet used that paramter.

More details can be found on the smb.conf man page... http://us4.samba.org/samba/docs/man/...mb.conf.5.html

I hope this helps.

Thank you for the response. I will try it and let you know!

I tried forcing users and forcing groups to no avail. It worked in keeping the users as 'nobody' and the group as 'users' but the permissions would change and the problem remained the same. After a bit more research I found a similar problem that was solved by disabling oplocks globally in the samba file. It's been a week now and they've had no problems. They've upgraded to Quickbooks as well and the installation went without a hitch in part because of the oplocks being disabled.