Another thing to check: are you calling growlnotify by its full path (/usr/local/bin/growlnotify)? If not, the application may not be getting the proper $PATH and so it may not find `growlnotify`
Tj On Sun, Jan 5, 2014 at 6:27 AM, Antonios <[email protected]> wrote: > I have a shell script including growlnotify to update me about its status. > When I start the script directly from the terminal, growlnotify works > normally. When the same script is started by a Mac OS X application such as > Automator or ChronoSync (when started as a backup pre-/post-flight script), > then no notifications are displayed. Anyone else having the same issue. Is > this by design, am I overlooking something... > I run the latest version of Mac OS X 10.9, Growl and growlnotify... > > Best regards > > Antonios > > -- > You received this message because you are subscribed to the Google Groups > "Growl Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/growldiscuss. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/growldiscuss. For more options, visit https://groups.google.com/groups/opt_out.
