Search results for query: *

So what's wrong with a push to speak button? I do like to keep things simple.

Thank you, elgrandeperro, I'll keep the commands and try the folder creation you suggest. Very many thanks to you all for all your very kind assistance.

Right, it works! It seems that the setfacl command finally did the trick. Thank you all very much for helping me through this. One final thing. So that that this will survive a server reboot, where should I place this command: setfacl -m...

Yes, danomac, there's only one group. What the problem is concerned with is that a Word file created and saved by one user in the group, cannot afterwards be edited by another user in the same group. The file always comes up as Read-only.

elgrandeperro and QatQat, there is absolutely no chance of any of the ladies at their terminals doing anything other than Windows things in Word. They even think that turning off the screen turns off the computer! Having run the setfacl command as shown above by Annihilannic, I asked them to...

So QatQat, are you suggesting I should run: chgrp -R feet /user/Common/DOCS find /user/Common/DOCS -type f -print0 | xargs -0 chmod 664 find /user/Common/DOCS -type d -print0 | xargs -0 chmod g+s 775 If so, that's what I'll do. I agree, I wish I knew what the cause of this is, so we could fix...

I ran the following commands again at site: chgrp -R feet /user/Common/DOCS find /user/Common/DOCS -type f -print0 | xargs -0 chmod 664 find /user/Common/DOCS -type d -print0 | xargs -0 chmod 775 but the problem remains: if one user saves a Word document in the folder /user/Common/DOCS and...

I've run the commands suggested by Annihilannic at 28 Feb 08 17:56 and expanded on by TonyGroves at 29 Feb 08 2:20 as to files and directories with spaces (they do have them all over the place!). As there' no one on site at the moment and I'm visiting site on Saturday, I'll give this a thorough...

Thank you so much. I think I understand that now. I'll set that up tomorrow morning and get them to test it, then I'll report back.

I'm afraid I'm very slightly lost there! OK, I create a crontab to run a script file every so often. The script file to contain, in my case: chgrp -R feet /user/Common/DOCS chmod -R 775 /user/Common/DOCS (do I need some other commands here?) Then you say to set the file permissions to 664 -...

That sounds just what I need. Thanks a lot. I guess then, that samba only works within those permissions - shows how green I am over this! I've run those commands (from my remote location) and will ask the site to carry out a test on Friday. Would I have to re-run the commands if the server...

Suse 9, Samba 3 and a dozen WinXP Pro users. Users saving M$ Word documents to a common area (/common/docs/) find that other users' documents are read-only. I've played around with force create mode and force directory mode (both currently set to 0775) in smb.conf until I'm blue in the face...