On Mon, Dec 15, 2008 at 11:32:22AM -0500, Sam Hartman wrote:
> I'm uncomfortable with the default to the normal hostname given what
> we know of the clustering code's security model.
Hmm, that's a fair point.
> When I worked on this I intended to create a hosts file template and
> generate it, but never got around to doing that.
But it doesn't seem very clean to have Invirt take over the /etc/hosts
file -- the sysadmin might have other entries they want to put there,
and they may also have some other convention for naming their internal
interfaces (e.g., $hostname.internal). Better is probably to add a
field to each host for its internal name / the name clustering should
use, and require it to be present rather than have a default.
On Mon, Dec 15, 2008 at 11:32:22AM -0500, Sam Hartman wrote:
> I'm uncomfortable with the default to the normal hostname given what
> we know of the clustering code's security model.
Hmm, that's a fair point.
> When I worked on this I intended to create a hosts file template and
> generate it, but never got around to doing that.
But it doesn't seem very clean to have Invirt take over the /etc/hosts internal) . Better is probably to add a
file -- the sysadmin might have other entries they want to put there,
and they may also have some other convention for naming their internal
interfaces (e.g., $hostname.
field to each host for its internal name / the name clustering should
use, and require it to be present rather than have a default.
Greg