>> The receiver is in "listening" mode but seems to only listen on UDP port >> 9887. Shouldn't it also listen on 23052? > > Yes.
So if you enable "listen" on your machine you get some output when calling $ netstat -nl | grep 23052 I get nothing. (Yet, it's announced via Bonjour) >>> Because you didn't tell growlnotify to address a specific host. >> >> I did try the "-H" option. And it works fine like this >> >> sender$ growlnotify -H receiver.local -P secret -m test >> >> This DOES bring up the notification on the receiver machine. > > Yup. So sending original notifications to another machine is working fine. Yup >> (as a side note: it segfaults when I don't specify a password). > > Oops. We'll have to look into that. Want me to open an issue for this? >> But that's really not what I was after. > > Oh, I lost track and thought you wanted to send original notifications. So > what you want is forwarding, then? Yup :) >> When setting up the forwarding I assumed that all local notification on the >> sender machine get forwarded to the receiving machine. So a local >> "growlnotify" is being forwarded to the receiver machine without me having >> to specify the destination. > > Correct. Only original notifications directly sent to a machine require you > to name that machine. Forwarding is notifications sent locally then getting > automatically forwarded to other machines. > > What happens when you do a local (non-network) growlnotify on the receiving > machine? That works just fine. It doesn't even fall back to NSDNC. 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.
