| 2 | | * it is not documented anywhere |
| 3 | | * rasserver does not throw an error if it doesn't have write access to `$RMANHOME/etc` |
| 4 | | * the behavior with the new rasmgr is unintuitive: when you change a rasdaman user (e.g. new password for `rasguest`), this file gets written to `$RMANHOME/etc/rasmgr.auth.713f3f57-bd3b-4211-ada6-bf88b49f81f1` or some similarly random bits appended. To make it effective, it needs to be renamed to `$RMANHOME/etc/rasmgr.auth` (as I figured out with some guesswork). I think what it should rather do is, make a backup of an existing rasmgr.auth, and then write the new rasmgr.auth. |
| | 2 | 1. rasserver does not throw an error if it doesn't have write access to `$RMANHOME/etc` |
| | 3 | 2. the behavior with the new rasmgr is unintuitive: when you change a rasdaman user (e.g. new password for `rasguest`), this file gets written to `$RMANHOME/etc/rasmgr.auth.713f3f57-bd3b-4211-ada6-bf88b49f81f1` or some similarly random bits appended. To make it effective, it needs to be renamed to `$RMANHOME/etc/rasmgr.auth` (as I figured out with some guesswork). I think what it should rather do is, make a backup of an existing rasmgr.auth, and then write the new rasmgr.auth. |
