Can you start a job without getting the job number spit back out?

BrianK · 12-13-2007, 02:42 PM

if I do some sort of "command&", the command gets run in the background, but a job number is spit back to stdout, like:

[1] 3746

... and then when it completes, it sends more to stdout like:

[1] + Done

Is there a way to suppress that output?

Why? In a script, I run several imagemagick commands at once (as many as the user asks for) & would prefer that the user didn't have to see the job numbers and pids flying across their screen. Kinda hard to weed out the other useful info that the script displays.

helptonewbie · 12-13-2007, 04:54 PM

This might work for you:-
just run it inside brackets (command &)
This will not show PID's but your user will still see normal output, if you want to get output into a file then
(command &) >> file
if you want error output and standard output in a file then
(command &) 2>&1 file
if you want error output in one file and standard output in another then:
(command & > file) >& file2

Hope that helps

BrianK · 12-13-2007, 05:00 PM

Quote:

Originally Posted by helptonewbie

This might work for you:-
just run it inside brackets (command &)
This will not show PID's but your user will still see normal output...

That worked perfect. Thanks!

custangro · 12-13-2007, 07:54 PM

Or...

Code:

command & >> /dev/null

BrianK · 12-13-2007, 08:08 PM

Quote:

Originally Posted by custangro

Or...

Code:

command & >> /dev/null

That doesn't work for me.

ls& >> /dev/null

in tcsh it doesn't work at all. In bash, it still displays the job number & pid.

:shrug:

gilead · 12-13-2007, 08:09 PM

Quote:

Originally Posted by custangro

Or...

Code:

command & >> /dev/null

That doesn't work on bash 3.2.15(2)-release under Slackware 11 - the job info is still output to the terminal here.