Seems as Bug #210 is still not solved in 3.0.0 Tried the recycle vfs module with different parameters. But all params seems to be ignored. The conf for the share is like [kolli] path = /u/samba/pc/kolli valid users = kolli root public = no writeable = yes printable = no nt acl support = yes recycle: repository=.Papierkorb recycle: keeptree = yes recycle: versions = yes browseable = yes guest ok = no Tried to set all param in on line like "vfs objects = recycle recycle: keeptree = yes..." Nothing changed. Tried "True" and "1" instead of "yes", didn't use blanks between ":" and between "=". But noting changed. Debuged with level 15 to see the vfs debug messages. But all params are reported as default like: [2003/11/18 13:44:35, 10] modules/vfs_recycle.c:recycle_repository(74) recycle: repository = .recycle Deleted files allways went to ".recycle" and the directory tree is not kept. Tried to only use one parameter (repository). But no effect. Seems the loadparm gets wrong or don't pass the parameter to the vfs module.
Addition: Sorry, by copy'n'paste one of the smb.conf params went away. The blank line should sound "vfs objects = recycle". I DON'T miss it in the conf. The current defs are: [kolli] path = /u/samba/pc/kolli valid users = kolli root public = no writeable = yes printable = no nt acl support = yes vfs objects = recycle recycle: repository=.Papierkorb browseable = yes guest ok = no
Bug still lives in 3.0.1pre3.
adding this to me list
I have the recycle module working ok with stable 3.0.1, however I have found that the ".recycle" directory is crated with permissions that are only writable by the user that first deletes a file and forces the creation of the ".recycle" directory. Should this be lodged as a separate bug, or is it ok to leave details here? Config used: [group_template] browseable = yes public = no writable = yes force create mode = 0660 force directory mode = 2770 vfs objects = recycle recycle:keeptree = 1 recycle:exclude = *.ldb *.tmp *.temp *.o *.obj ~$* [test-share] copy = group_template path = /var/test-share valid users = @sys Even with the "force mode" options directory is created as follows: $ ls -lasi /var/test-share/ total 2 2190346 1 drwxrwsr-x 3 scperry sys 72 Jan 9 13:38 . 4 1 drwxr-xr-x 27 root root 712 Jan 9 10:49 .. 1842336 1 drwx--S--- 2 scperry sys 96 Jan 9 13:38 .recycle
I'm marking this as fixed since it is ok in 3.0.1. There's another bug report (bug 1040) that covers the permissions on newly created directories.
Sorry, but the bug with the not supplied params still live in 3.0.2 Seems to me, that everyone uses the defaults and get happy with. 3.0.2 still do not deliver params to the vfs object "recycle". Tried every kind of parameter format (seperate lines, one line, spaces between keywords). No effect.
Rudolf, I copied you original confi options and it works fine. I cannot reproduce any obvious errors. The repository directory is created as expected, the directory tree is maintained. Please provide a level 10 debug log of the error you are seeing.
Mea culpa! Sorry. Don't know where i got the faulty module. Sorry agein. Run's as you described. I didn't get the "exclude" parameters to work as expected. But may be a wrong config. Didn't investigated now. Thank's for your patience.
probably old recycle module. closing again.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.