Because the folder is created immediately you can’t rename it again (unless you ssh to the server and use a privileged account to rename it).

I realise this is not a perfect solution but at least it stops family being able to accidentally delete stuff.

The above works well apart from one thing.
When I create a new folder on Windows XP I cannot rename the folder during the create folder process.
I get
New Folder
New Folder (1) etc.
Is there a way around this?

Thanks

Thanks!

That seems to work a treat! I have only done a quick test but I copied over a directory structure with some files, tried deleting through Nautilus – failed. Then I copied a new file into one of the new subdirectories and it worked. And I couldn’t delete again it either.

I’ll update the post. And I’ll let you know if anything further crops up.

Thanks again,

Alan

The actual problem is that our “current” configuration blocks deletion of first-level children of the root directory, but it doesn’t put any constraint on the children of the subdirectories.
In fact, the problem is that the sticky bit is not cascaded on the subdirectories, i.e. the structure we’re building is not fully recursive.

A possible solution:
directory mode = 3770
force directory mode = 3770

The first octal number basically forces the sticky bit (+1) and the SGID bit (+2). This should make every files and directory dropped in the share a perfect copy of the root directory (as far as permissions go).

Let me know if it works for you

I can drop a tree into the drop-box, sorry. I thought I couldn’t add files to the drop-box later on inside the newly created tree structure, but having just tried this, I was totally wrong.

But the scary part, is you can delete everything inside the top-level directory…

In my test I opened Nautilus and mounted my music drop-box share. I dragged a small structure from my local disk to the drop box and it copied in fine:

$ ls -l tolc-1.5/
total 40
drwxrws— 2 nobody shared 4096 2008-12-01 20:38 css
-rwxr–r– 1 nobody shared 2988 2008-12-01 20:38 frontpage.php
drwxrws— 2 nobody shared 4096 2008-12-01 20:38 images
-rwxr–r– 1 nobody shared 5889 2008-12-01 20:38 index.php
drwxrws— 2 nobody shared 31 2008-12-01 20:38 js
-rwxr–r– 1 nobody shared 0 2008-12-01 20:38 params.ini
-rwxr–r– 1 nobody shared 2958 2008-12-01 20:38 templateDetails.xml
-rwxr–r– 1 nobody shared 2931 2008-12-01 20:38 templateDetails.xml~
-rwxr–r– 1 nobody shared 10962 2008-12-01 20:38 template_thumbnail.png

But now, for some reason I do not fully understand, if I highlight the top-level directory in Nautilus (tolc-1.5) and hit enter and accept the “permanently delete” option, I get a pop up saying it can’t delete tolc-1.5 but everything below it has been removed… The directory is now completely empty.

One thing to note is the *files* are being created rwxr–r– whereas prior to your suggestion they were being flagged rw-r–r–.

Thanks.

Alan