From: Chris T. <chr...@gm...> - 2011-10-18 07:26:05
|
Dmitriy, I'm confused. I uploaded the files into the top collection, /db/tbrc which is where the <default-permissions/> is placed in the collection.xconf file for the top collection /db/tbrc. Unless you're saying that I have to have a collection.xconf for /db itself which I don't think is what you're saying. Surely, I don't need to add <default-permissions/> to collections /db/tbrc/A and /db/tbrc/B and so on in order to control the default permissions for files uploaded into collection /db/tbrc?? Thanks, Chris On Oct 18, 2011, at 1:02 PM, Dmitriy Shabanov wrote: > add default-permissions to each collection.xconf, not just top one. > > I did write: it will look up to first configuration. But if that first configuration don't have default-permission, then it use internal-default one. That is current behavior. > > On Tue, Oct 18, 2011 at 12:11 PM, Chris Tomlinson <chr...@gm...> wrote: > Dmitriy, > > The collections are structured as: > > /db/tbrc > /db/tbrc/A > /db/tbrc/B > > and I have collection.xconf files for /db/tbrc and /db/tbrc/A and /db/tbrc/B. There is no collection.xconf for /db > > However, for the purposes of this test I only put the <default-permissions/> in the collection.xconf for /db/tbrc and then did the uploads into the collection /db/tbrc. I would assume the presence of collection.xconf files below /db/tbrc would have effect on the uploads into /db/tbrc. > > I note that back on 4 Aug, Efraim Feinstein remarked: > >> (3) The obvious way to do (2) is the default-permissions element in >> conf.xml. As far as I can tell, setting the resource parameter to 770 is >> doing nothing. > > So apparently he was having difficulties in the same area. I saw no replies regarding his observation. > > Chris > > > > On Oct 18, 2011, at 12:47 PM, Dmitriy Shabanov wrote: > >> is it only collection.xconf that you have? >> >> On Tue, Oct 18, 2011 at 11:23 AM, Chris Tomlinson <chr...@gm...> wrote: >> >> I added the defaults as you indicated to the collection.xconf for a collection /db/tbrc >> >>> <collection xmlns="http://exist-db.org/collection-config/1.0"> >>> <default-permissions resource="0774" collection="0774"/> >>> <triggers> >>> <trigger event="store,remove,update" class="org.exist.versioning.VersioningTrigger"> >>> <parameter name="overwrite" value="no"/> >>> </trigger> >>> </triggers> >>> </collection> >> >> I shutdown the DB and removed the redundant lines from the conf.xml and restarted the DB and then uploaded a file via the admin.xq Browse Collections and also uploaded a file via the client.sh command line put. In both instances I am still seeing: >> >> "rw-r--r--" >> >> For the resulting permissions. Only the user that uploaded can delete and no updates can happen. >> >> >> >> -- >> Dmitriy Shabanov > > > > > -- > Dmitriy Shabanov |