On Apr 2, 2010, at 01:50:37, adam n wrote: > Someone suggested to try: "open -b com.Growl.GrowlHelperApp" from the command > line, but that doesn't completely work to get Growl running, because if i do: > (in system preferences) click the Stop Growl button, then "open -b > com.Growl.GrowlHelperApp", then "growlnotify -m "test" ", it gives the "could > not find local GrowlApplicationBridgePathway, falling back to NSDNC" error."
That message means, essentially, “Growl isn't running”. > But if I click Stop Growl, then click Start Growl, then do "growlnotify -m > "test" ", it works fine. So it seems like doing "open -b > com.Growl.GrowlHelperApp" doesn't start all the necessary processes to run > Growl. It does. The reason why it doesn't work after stopping Growl is that you turned Growl off. Growl will detect when it's turned off and quit immediately. That's what it's supposed to do: The user told it to go away, so it goes away and stays away. open -b is the correct solution. -- 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.
