Personally, I think that complicates things.
I'd keep one variable for the port, regardless of whether it is
unicast, or multicast. What might work, is that if msg_channel = a
local interface, listen, else send to msg_channel.
Also, do the mute/deaf flags still apply? So, you can mute a gmo
doh.
clearly.. i need to change that.
msg_port_out
msg_port_in
perhaps? i meant.. it only open the port if msg_port_in is explicitly
set.
excuse me while i go hang my head in shame and quickly alter the code.
-matt
On Thu, 2004-02-26 at 20:42, Josh Durham wrote:
> > if it's a unicast channe
if it's a unicast channel, gmond configures itself a little
differently.
gmond will send messages on the unicast channel (which will write to a
single host) but it will NOT listen to unicast messages unless
"msg_port" is explicitly set.
I may be missing something here, but how do you configure
On Thu, Feb 26, 2004 at 07:17:05PM -0800, Matt Massie wrote:
> i think brooks comment on the compressed XML is right on target. it
> doesn't make sense to make put zlib compression on a separate port. it
> make more sense to have a web server port (and the old style simple tcp
> socket as well).
ok
so the title is a little extreme (but true).
i've been workin' hella hard to get the 2.6.0 release ready to go. the
2.5.7 release i've talked about (w/ the great solaris stuff and xml
compression).. got morphed into 2.6.0 before it was released. we might
as well go for the gold here and give
