On Thu, 2008-10-09 at 16:00 +0200, Marco Mornati wrote: > On Thu, 2008-10-09 at 09:49 -0400, seth vidal wrote: > > [...] > > > > This only works if you only have a single overlord. > Why are you saying is working with a single overlord configuration? > > > > With minion-to-minion communication you want to store it on the side > > that is trying to send it to you. > > > > Think of it like smtp. If the receiving system is down the message waits > > and queues on the sending system's SMTP server. > Yes normal. > What I thought was an handshake system from client to server to prevent > polling. > > My minion has only one certmaster and with it will make the handshake. > My certmaster has the queue information for all linked machines... > > (Maybe there is something I'm ignoring) :) > This piece is only partially implemented - but think of a time when minions can issue commands to other minions. that's what I'm talking about. So the issue I'm concerned with is minion1 issuing a command to minions3, 4 and 5. 4 is not up so the command holds on minion1 until 4 is up (or until some timeout period). See what I mean? -sv _______________________________________________ Func-list mailing list Func-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/func-list
