Re: [Merge] ~epics-core/epics-base/+git/asLib:as-hostname into epics-base:7.0

[mdavidsaver via Core-talk <core-talk@aps.anl.gov>]

Review: Needs Fixing

> if a host-name cannot be found, this will cause the IOC to start up with all access disabled. Is this the behavior that we actually want?

That's a fair point.  As I think about it, there is no reason to fail the whole load if one host doesn't lookup.  It would be easy enough to fill in "unresolved" instead of an IP, print a warning, and continue.

(personally, I'd like to eliminate read access restrictions all together)

> something that could our IT group might do at any time

To some extent, this could be mitigated by including both hostname and IP for some important hosts.  eg, hosts which can trigger ACF reload.

Ultimately though, turning this feature on implies an acceptance of this risk.

-- 
https://code.launchpad.net/~epics-core/epics-base/+git/asLib/+merge/358822
Your team EPICS Core Developers is subscribed to branch epics-base:7.0.