Curious if others are having problems with the installation and usage of
growlnotify. We've deployed the software which I snapshot via Composer.
Curious how others have deployed and best practices on your network.
During snapshotting I turned OFF the following:
+ listen for incoming notifications
+ forward notifications
+ check for updates automatically
+ inform growlnotify when a notification is clicked
We've deployed the software and then run the following simple bash script:
#!/bin/sh
/usr/local/bin/growlnotify -a Self Service -m "The Growl application has
been successfully installed on your Mac. You may resume your work."
exit 0
When running that script from CLI, everything's fine. When that same script
is pushed via casper, the target system hangs on the growlnotify process. As
a result, it stops the jamf client from working. At least until that Mac is
rebooted. Otherwise, we need to forcequit the growlnotify process to unlock
the machine and allow jamf to continue working.
I'm at a loss and could use some groupthink, if ya got anything to share.
Cheers,
David Koff
Mac SysAdmin
The J. Paul Getty Trust
Lost Angeles, Calipornia
