Re: [help-gnubatch] hostedit issues?

[Wechsler, Steven]

Perhaps you could set it up so that any host can act as a master for any other; once a new host is setup and is talking to one host, it grabs all the other hosts that the master knows about, and continues to poll at regular intervals to find out if there are any new ones.

 

Steve

 

From: help-gnubatch-bounces+address@hidden [mailto:help-gnubatch-bounces+address@hidden On Behalf Of John Collins (Xi Software Ltd)
Sent: Tuesday, January 17, 2012 5:19 PM
To: address@hidden
Subject: Re: [help-gnubatch] hostedit issues?

 

On 17/01/12 21:21, Wechsler, Steven wrote:

While we’re on the subject, when I have multiple hosts, do I need to run the hostedit on each host to add all other known hosts. For example, if I have hosts A, B, C and D, do I need to tell host A about B, C and D; host B about A, C and D, etc? And when I add a new host, I need to tell every old host about it? There is no automatic cascading of host information?

 

Yes alas, this is wrong. It ought to be by an IP block or *.foo.com or something to allow/deny access.

I must do that soon like in the next week as I'm hitting a problem in that area with the new Windows clients.