Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
12-13-2007, 02:42 PM
|
#1
|
Senior Member
Registered: Mar 2002
Location: Los Angeles, CA
Distribution: Debian, Ubuntu
Posts: 1,334
Rep:
|
Can you start a job without getting the job number spit back out?
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.
|
|
|
12-13-2007, 04:54 PM
|
#2
|
Member
Registered: Aug 2006
Location: England Somewhere
Distribution: Mandriva, PCLinuxOS, Karoshi, Suse, Redhat, Ubuntu
Posts: 518
Rep:
|
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
|
|
|
12-13-2007, 05:00 PM
|
#3
|
Senior Member
Registered: Mar 2002
Location: Los Angeles, CA
Distribution: Debian, Ubuntu
Posts: 1,334
Original Poster
Rep:
|
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!
|
|
|
12-13-2007, 07:54 PM
|
#4
|
Senior Member
Registered: Nov 2006
Location: California
Distribution: Fedora , CentOS , RHEL
Posts: 1,979
|
Or...
Code:
command & >> /dev/null
|
|
|
12-13-2007, 08:08 PM
|
#5
|
Senior Member
Registered: Mar 2002
Location: Los Angeles, CA
Distribution: Debian, Ubuntu
Posts: 1,334
Original Poster
Rep:
|
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:
|
|
|
12-13-2007, 08:09 PM
|
#6
|
Senior Member
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,141
Rep: 
|
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.
|
|
|
All times are GMT -5. The time now is 04:17 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|