Howdy --
I have a number of different installed instances of BaseX (7.2 release, current snapshot, local build, etc), each with a .basex file pointing against the same DBPATH.
I've frequently noticed when switching between trees that "admin" account switches back to its default password, and my more limited user accounts disappear and need to be recreated.
Are these stored somewhere other than DBPATH?
I've frequently noticed when switching between trees that "admin" account switches back to its default password, and my more limited user accounts disappear and need to be recreated.
Global users are stored in the .basexperm file, while local permissions will be stored in the meta file of a database (inf.basex).
I didn't come across this issue before.. Do you have a reproducible example?
Thanks, Christian
PS: sorry for delaying your other mails; seems this is getting a very busy week.
On 04/03/2012 03:43 PM, Christian Grün wrote:
I've frequently noticed when switching between trees that "admin" account switches back to its default password, and my more limited user accounts disappear and need to be recreated.
Global users are stored in the .basexperm file, while local permissions will be stored in the meta file of a database (inf.basex).
Thank you -- I think this actually answers my question adequately. I was expecting global users to be stored somewhere under the shared DBPATH, and it could simply be that the .basexperm files were never written for the other trees. If I can validate any larger issue, I'll get back with a reproducer at that time.
That said, I would suggest parameterizing the location of this file as a future enhancement -- when wearing my sysadmin hat, it's often undesirable for applications to have any kind of write permissions to the location their binaries are installed; indeed, in the UNIX world it's not unheard of to have binaries coming from a completely read-only disk or network store, making it *impossible* to write data back to that location (as opposed to an explicitly writable area under /var or such).
You might want to check the "Configuration" Wiki page [1], which described how to change the path to all .basex... files.
Hope this helps, Christian
[1] http://docs.basex.org/wiki/Configuration ___________________________
Thank you -- I think this actually answers my question adequately. I was expecting global users to be stored somewhere under the shared DBPATH, and it could simply be that the .basexperm files were never written for the other trees. If I can validate any larger issue, I'll get back with a reproducer at that time.
That said, I would suggest parameterizing the location of this file as a future enhancement -- when wearing my sysadmin hat, it's often undesirable for applications to have any kind of write permissions to the location their binaries are installed; indeed, in the UNIX world it's not unheard of to have binaries coming from a completely read-only disk or network store, making it *impossible* to write data back to that location (as opposed to an explicitly writable area under /var or such).
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
basex-talk@mailman.uni-konstanz.de
-
Charles Duffy -
Christian Grün