However, I'm having second (third?) thoughts about the idea of having a second or third set of default values for these parameters, which are sometimes are used, and sometimes ignored.
Probably the most confusing is EPICS_PVAS_PROVIDER_NAMES. A default value of "local" will actually prevent QSRV from starting! ("local" is the name used by pvDatabaseCPP) The actual default is "<all>", which selects all registered server-type ChannelProviders.
I'm tempted to say that it would be better to defer to the "pvasr" iocsh function, which can print the configuration actually being used by the running server (in IOCs).
That said, the set of parameters which I think should be advertised are:
pvAccessCPP will now use these parameters.
However, I'm having second (third?) thoughts about the idea of having a second or third set of default values for these parameters, which are sometimes are used, and sometimes ignored.
Probably the most confusing is EPICS_PVAS_ PROVIDER_ NAMES. A default value of "local" will actually prevent QSRV from starting! ("local" is the name used by pvDatabaseCPP) The actual default is "<all>", which selects all registered server-type ChannelProviders.
I'm tempted to say that it would be better to defer to the "pvasr" iocsh function, which can print the configuration actually being used by the running server (in IOCs).
That said, the set of parameters which I think should be advertised are:
EPICS_PVA_ADDR_LIST AUTO_ADDR_ LIST BROADCAST_ PORT SERVER_ PORT BEACON_ ADDR_LIST SERVER_ PORT INTF_ADDR_ LIST BROADCAST_ PORT
EPICS_PVA_
EPICS_PVA_
EPICS_PVA_
EPICS_PVAS_
EPICS_PVAS_
EPICS_PVAS_
EPICS_PVAS_