09-13-2008
unable to execute background job
I am unable to execute the below command in background. Plz suggest.
#> ./test input >out &
[1] 913618
[1] + Stopped (SIGTTIN) ./test input >out &
Suresh
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I try to run a script as background job.
script:
#!/usr/bin/csh
/usr/bin/date +20%y-%m-%d > ~/datsql.txt
If I start it I got this output:
tac> ./datermitteln&
293
+ Stopped (SIGTTOU) ./datermitteln&
I insert the following line inside my script, but without any... (3 Replies)
Discussion started by: joerg
3 Replies
2. UNIX for Dummies Questions & Answers
Hiya,
Recently I've run a few scripts in the foreground, but have realised later they should of been better nohup'd and placed in the background. I understand how to change a foreground job into a background one, but how would put the job into the nohup state?
Thanks (1 Reply)
Discussion started by: rdbooth
1 Replies
3. UNIX for Dummies Questions & Answers
on gnome i open a terminal and run wget http://soommmething & in the background. because wget shows me downloading progress percentage and download speed continuously, I exit the gnome-terminal
after a while i want to see the download percentage but dont know how. my ps -u myname shows that... (3 Replies)
Discussion started by: babayeve
3 Replies
4. Shell Programming and Scripting
hi, i am just wondering that wen we give the following code we make a process run in background...can the viceversa be performed?i.e can this be made foreground again
# sleep 75&
21751
# (4 Replies)
Discussion started by: sandilya
4 Replies
5. Shell Programming and Scripting
Hi all,
I am currently facing a problem when i am submitting a script to run in the background to collect statistics round the clock on an AIX box. I don't have root authority nor can I set it in cron.
So when i submit the job, it runs fine, but won't let me signoff. It prompts me that... (2 Replies)
Discussion started by: tansha
2 Replies
6. UNIX for Advanced & Expert Users
Hello - I submitted one background job last night and it completed today morning.I want to know exact time the job completed.
I submitted backgroung job like this
nohup cp -Rp /opt/apps/prod/proddb/proddata . &
I want to know when above job completed on UNIX server.Above command... (9 Replies)
Discussion started by: Mansoor8810
9 Replies
7. Shell Programming and Scripting
Hello Everyody,
Having a doubt.
sort file1 &
when we sent a job to the background it returns
Job Number
PID
again if we want to ... (1 Reply)
Discussion started by: knroy10
1 Replies
8. Shell Programming and Scripting
load_cursor_stmt()
{
ls /db/admin/ddl/rmn01000/load_cursor*.sql|while read file
do
echo "${file}"
`nohup db2 -tvf "$file" \&`
done
}Error:
-------
/admin/ddl/rmn01000/load_cursor5.sql /db/admin/ddl/rmn01000/load_cursor6.sql
+ read file
+ echo... (3 Replies)
Discussion started by: Hangman2
3 Replies
9. Shell Programming and Scripting
How to bring a backgroud job say sample_script.sh to foreground (4 Replies)
Discussion started by: rafa_fed2
4 Replies
bg(1) General Commands Manual bg(1)
NAME
bg - Runs jobs in the background
SYNOPSIS
bg [job_id...]
Note
The C shell has a built-in version of the bg command. If you are using the C shell, and want to guarantee that you are using the command
described here, you must specify the full path /usr/bin/bg. See the csh(1) reference page for a description of the built-in command.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
bg: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
None
OPERANDS
Specifies the job to be resumed as a background job. If no job_id operand is given, the most recently suspended job is used. The format of
job_id is described in the Jobs section of the ksh(1) reference page.
DESCRIPTION
If job control is enabled (see the description of set -m in the ksh(1) reference page), the bg utility resumes suspended jobs from the cur-
rent environment by running them as background jobs. If the job specified by job_id is a job already running in the background, the bg
utility has no effect and will exit successfully.
Using bg to place a job into the background causes its process ID to become "known in the current shell execution environment", as if it
had been started as an asynchronous list. See the Jobs section of the ksh(1) reference page.
RESTRICTIONS
If job control is disabled, the bg utility exits with an error and no job is placed in the background. The bg utility does not work as
expected when it is operating in its own utility execution environment because that environment has no suspended jobs.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of bg: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale used to
affect the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the
processing of LC_MESSAGES.
SEE ALSO
Commands: csh(1), fg(1), jobs(1), kill(1), ksh(1), Bourne shell sh(1b), POSIX shell sh(1p), wait(1)
Standards: standards(5)
bg(1)