Use Growl to monitor long-running shell commands

Search

From our Sponsor...

User Functions

Don't have an account yet? Sign up as a New User
Lost your password?

What's New:

Hints

No new hints

Comments last 2 days

Links last 2 weeks

No recent new links

What's New in the Forums?

The Editor's Corner...

Here are some of my (robg) other projects...

•	The Robservatory My blog - Macs, tech, etc.
•	Mac OS X Power Hound The best of Hints in print
•	Inside iWork An iWork training DVD
•	Macworld Column, features, online...

Hints by Topic

News from Macworld

The macosxhints Poll

What version of OS X are you running as your main OS?

Other polls | 11,398 votes | 42 comments

Use Growl to monitor long-running shell commands | 22 comments | Create New Account

Click here to return to the 'Use Growl to monitor long-running shell commands' hint

The following comments are owned by whomever posted them. This site is not responsible for what they say.

Use Growl to monitor long-running shell commands
Authored by: Lutin on Fri, Oct 12 2007 at 4:34AM PDT

I had implemented your solution before reading this hint.
Unfortunately, I often realize a command will take longer than expected once it's already running (like a slow server with wget...).

The idea in the hint is really great.
Each reader will pick what he prefers. And both hints aren't exclusive (but you might want to add some code to prevent a double notification).

Use Growl to monitor long-running shell commands
Authored by: 4ndrew on Sat, Oct 13 2007 at 2:23PM PDT

See my solution: http://www.macosxhints.com/comment.php?mode=view&cid=91037