diverging file name conventions

[Peter Baumann]

it is aesthetics, but still we should aim at coherent naming.
Counter example in $RMANHOME/etc:

• log-server.conf vs wms_service.properties
• backups generated:
  • petascope.properties.01-15-2016_14-17-33.bak
  • petascope.properties.11-26-2015_11-59-41.bak
  • petascope.properties.bak.pre9.0

As some files are freshly introduced 9.2 may be our chance to converge it somewhat.

[Bang Pham Huu]

I'd like to suggest change log rasserver file name in install/log also (e.g 3f880f60-e44e-4157-8865-54249af5a984.019770.log)

[Peter Baumann]

Replying to bphamhuu:

I'd like to suggest change log rasserver file name in install/log also (e.g 3f880f60-e44e-4157-8865-54249af5a984.019770.log)

It's not about changing existing (and long-standing) practice, but conversely bringing new items in sync with existing conventions. Changing log file names is changing user visible behavior = potentially creating trouble, while not adding functionality.

[Bang Pham Huu]

Replying to pbaumann:

Replying to bphamhuu:

I'd like to suggest change log rasserver file name in install/log also (e.g 3f880f60-e44e-4157-8865-54249af5a984.019770.log)

It's not about changing existing (and long-standing) practice, but conversely bringing new items in sync with existing conventions. Changing log file names is changing user visible behavior = potentially creating trouble, while not adding functionality.

May be I have misunderstood the content of this ticket but regard to log file and from your comment, I know this has changed the user behavior as from document "rasdaman installation and Administration guide", page 39

standard output.
(default: $RASDAMAN/log/serverid.log)

or the old log I got is "N5.014930.log" (that is convention) not as now "83b3eb0e-1771-4542-ae72-21c41a8a309f.030624.log". So if you agree with the new name then I will have no other comment.

[Dimitar Misev]

I get it we want to change wms_service.properties to wms-service.properties? Who uses this configuration, can't it be integrated in petascope.properties anyway?

In 9.3.1 we have:

log-client.conf
log-rasmgr.conf
log-server.conf
rasmgr.conf
petascope.properties
secore.properties
wms_service.properties

[Peter Baumann]

ok, we might do a general cleanup, but let us be careful about compatibility. Maybe collect all and go for 10.0?