growlnotify not responding

[powdR]

First, thanks a lot for Growl!

We have a network with a OSX Server 10.5.3 and three 10.5.3 clients.
I want to be able to send a sticky growlnotify to the other machines.

I ran the install in CLI which appeared to run fine.
running man to read the manual did not work. I read the forums and moved the file, then that worked.

Then, when I run growlnotify, what happens is that cursor just jumps to the next line and stays there
indefinitely. Nothing happens. When i ctrl-c I am returned to the shell.

What do I do wrong? Please advise! :-)

best regards from Oslo,
//Haakon Storm

[boredzo]

… when I run growlnotify, what happens is that cursor just jumps to the next line and stays there
indefinitely. Nothing happens. When i ctrl-c I am returned to the shell. …

What version number does Growl show in the About tab of its preference
pane in System Preferences?

What is the output of `growlnotify --version`?

[ximon]

I have exactly the same problem.

xiMac:~ ximon$ growlnotify --version
growlnotify 1.1.4
Copyright (c) The Growl Project, 2004-2008

Mac OS X 10.5.4 (Intel)

[boredzo]

I have exactly the same problem.

Please take a sample of growlnotify using [url=x-man-page://1/sample]the sample command[/url] and post it here.

[ximon]

OK no worries, I wasn't using the -m switch, it's my own stupid fault.

[boredzo]

OK no worries, I wasn't using the -m switch, it's my own stupid fault.

Ah, OK. I went ahead and added a prompt message in r4905 (just now), to avoid future confusion of this sort.

Code: Select all

% build/Development/growlnotify foo            
Enter a notification description, followed by newline, followed by Ctrl-D (End of File). To cancel, press Ctrl-C.

[kabelallergie]

What is wrong with the -m switch? Growlnotify is not working here anymore using 10.5.4. What message do you dislay whithout the -m switch? Leaving that switch away or using --message. Didn't help. Growlnotify is behaving exactly as described above.

[boredzo]

What is wrong with the -m switch?

Nothing. It's working fine.

Growlnotify is not working here anymore using 10.5.4.

What version of growlnotify? (growlnotify --version)

What message do you dislay whithout the -m switch?

None. That's what causes the confusion: People don't realize that growlnotify is waiting for input.

Leaving that switch away or using --message. Didn't help.

--message is the same as -m, so using --message should also solve the problem. (I just tested this and it works.)

Growlnotify is behaving exactly as described above.

What's the specific command line that you entered?