Task #10187 (new)
Opened 11 years ago
Last modified 8 years ago
4.4.x fixes suggested by Bernhard.
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | critical | Milestone: | Unscheduled |
| Component: | Services | Version: | n.a. |
| Keywords: | n.a. | Cc: | jburel, Bernhard.Hollaender@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by jmoore)
- Allow configuring the default permissions for new groups
- Handle non-writeable config.xml files (See PR641)
- Make index creation/deletion more fault tolerant
- Check sequence creation doesn't assume start values of 1.
Change History (5)
comment:1 Changed 11 years ago by jmoore
comment:2 Changed 11 years ago by jmoore
- Description modified (diff)
comment:3 Changed 11 years ago by jmoore <josh@…>
(In [8c9bd38e5f55a7b111a3abfb45263c9dea875ec6/ome.git] on branch develop) Handle read-only etc/grid/config.xml files (See #10187)
For installations which should not be modified by non-syadmins,
it is useful to allow the etc/grid/config.xml to be locked
(chmod 444). The only limitation is that the modification of
the active profile can no longer be modified via OMERO_CONFIG
or bin/omero config def.
All calls to bin/omero config which would modify config.xml
now print an error message. (bin/omero config def is somewhat
special since without an argument it does not modify config.xml
but with an argument it does)
Similarly, all calls to bin/omero admin check that either the
file is lockable or that no profile has been selected.
comment:4 Changed 11 years ago by Josh Moore <josh@…>
(In [1a84b850cc5f85e9e670005c998304b9648651b0/ome.git] on branch develop) Merge pull request #651 from joshmoore/rebased/develop/read-only-config-xml
Handle read-only etc/grid/config.xml files (See #10187) (rebased onto develop)
comment:5 Changed 8 years ago by jamoore
- Milestone changed from 5.x to Unscheduled
Jean-Marie, any thoughts on getting some of these into 4.4.6?