On Wed, Apr 14, 2010 at 16:30, Peter Hosey <[email protected]> wrote: > 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?
[10.5 machine] ---forwarding via UDP--> [10.6 machine in "listen" mode] [10.5 machine] --NSDNC--> [10.5 machine] (only locally) I would have thought only 10.6 should have a UDP port listening on 9887. This is why I didn't get that you would expect a UDP socket listening on the 10.5 machine. > 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. ....but now that you say DO is being used it makes more sense. That said - nothing is listening on port 9887 on the 10.5 machine. So far I've never used DO before. From the sources it looks like we should have TCP socket though (GROWL_TCP_PORT = 23052) though. No? > 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? This is just from the 10.5 machine (the one with “falling back to NSDNC”) $ ps axww | grep -F Growl 121 ?? S 0:01.11 /Library/PreferencePanes/Growl.prefPane/Contents/Resources/GrowlHelperApp.app/Contents/MacOS/GrowlHelperApp -psn_0_61455 435 s000 R+ 0:00.00 grep -F Growl but I see the helper app running on both machines. Just out of curiosity I've also turned on "listen" on the 10.5 machine. I do have the UDP port open there now as well. But that didn't change a thing. The 10.5 machine still uses NSDNC. Still no sign from the TCP port sockets. Looking at the console log of the 10.5 machine and then looking at "MD5Authenticator.m" I am wondering. "received signature doesn't match computed signature" should that just mean the password is wrong? 4/14/10 5:55:31 PM GrowlHelperApp[475] GrowlHelperApp Authentication failed while forwarding to 192.168.1.15:3162 ((null)) 4/14/10 5:56:08 PM GrowlHelperApp[478] GrowlHelperApp authentication failure: received signature doesn't match computed signature 4/14/10 5:56:08 PM GrowlHelperApp[478] GrowlHelperApp Authentication failed while forwarding to 192.168.1.15:3162 ((null)) I've tried a couple of times and are 100% I've put in the passwords correctly. I even checked directly in Keychain and they both are the same. Really not sure what else to do except for compiling and debugging. And further ideas from your side? 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.
