On Apr 14, 2010, at 05:58:43, Torsten Curdt wrote:
> Looking at the sources I know understand what NSDNC means:
> NSDistributedNotiticationCenter. So this is not using the UDP path at all on
> the local system.
Good catch.
This isn't documented very well, but you need to specify a recipient host when
using UDP. -u is ignored if you don't name a recipient host.
> That said I would have thought that a socket only will be opened if Growl is
> in "listen" mode. As that machine is only sending I don't see the need for a
> socket if locally all gets exchanged through the NSDNC.
Huh?
The DNC is the last resort. For local notifications, Cocoa Distributed Objects
to the local Growl DO pathway is preferred, and if that succeeds (which it
always does for almost everyone), DNC doesn't get used. For remote
notifications (those sent to a specific host), DNC is never used.
Try this on the sending machine (the one where you got the “falling back to
NSDNC” message):
ps axww | grep -F Growl
What's the output?
--
You received this message because you are subscribed to the Google Groups
"Growl Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/growldiscuss?hl=en.
