Open tatobi opened 11 years ago
Thanks for the bug and sorry for the long delay.
Can you paste the relevant part of your config here?
Which OS and which revision of RioFS are you running? Can you please try again with the latest revision?
Does this problem also occur when setting fmode/dmode via command line, i.e. --fmode=0777?
What do you mean exactly with weird and unpredictable rights? Could you paste the output of such a directory listing?
ACLs with fuse is tricky stuff, especially as the storage system we are accessing (S3) has no idea of ACLs.
It would be also great if you could share your use case why you need to play with these options.
I am having the same problem as this. No matter what I set fmode/dmode to it gives weird permissions.
I am also suffering from this problem.
When reading the integer from the default xml config it is ignoring the leading zero. As an example the setting 0777 becomes 777 and gets the permissions r----x--t.
after reading this site where the user mentions setting the fmode to 511 and getting the 777 permissions: http://blog.smoothlinux.com/post/increasing-riofs-performance I realized that the values in the config.xml are decimal numbers, that are converted to octal, which behaves as you would expect... So to get 777, enter 511, for 755, enter 493, for 700, enter 448
Set fmode, dmode to 0777, 0777 in default xml config gives weird rights. Changing to any well known ACL value e.g. 775 or any others give unpredictable right on the root folder. I set it to 0777 in dir_tree.c, define DIR_DEFAULT_MODE S_IFDIR | 0755 -> define DIR_DEFAULT_MODE S_IFDIR | 0777 and recompiled then I gave the desired result on the root folder. I think the "allow_other" cmd line value should override the fmode,rmode,guid,uid values. I would be very happy with a config value for override all of these values because a lot of people does need it really, just access to the S3 simply for everybody, this is why I chosen the riofs over s3fs, a days of suck with gids, uids, modes... err