On Thu, Apr 8, 2010 at 02:14, Torsten Curdt <[email protected]> wrote: > On 08.04.2010, at 01:58, Peter Hosey <[email protected]> wrote: > >> On Apr 7, 2010, at 14:18:34, Torsten Curdt wrote: >>> >>> Doing a "growlnotify" on the forwarding machine I do get a local >>> notification message. >>> I also do get a "could not find local GrowlApplicationBridgePathway, >>> falling back to NSDNC" in the console though. >> >> >> That's curious. You should only get that message when Growl isn't running, >> but if Growl isn't running, you shouldn't see a notification locally (and >> the UDP send should fail). > > Well, that leads to the question why it thought it wasn't running when it > was. > > >> What if you stop and restart Growl on that machine? > > Tried that. I think I even rebooted the machine. But let me try that again. > Just to be sure.
Sorry for the delay. But I can confirm also after a reboot I see the same behavior. The "NSDNC" message on 10.5 and nothing arriving on my 10.6 machine. 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. Which explains why the local notification works still the connection fails. 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. Or am I misinterpreting things here? cheers -- Torsten -- 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.
