05-25-2005
Quote:
Originally Posted by blowtorch
Emil,
I dont think that is possible. Once a process loses its controlling terminal, you can no longer see the output that it would be sending to that terminal. A workaround would be to redirect the stdout and stderr to a file and view the file later.
.... or 'nohup' the process and 'tail -f nohup.out'
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. 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
4. 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
5. AIX
Guys,
We use AIX 5.3 at our work place. I only in my team have a strange problem of not able run jobs background. Other colleagues are able to run without any problem.
Once I kick off background job using nohup and & command, It immediately stops. The following error I get when I run.
... (2 Replies)
Discussion started by: anandsbr
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
How to bring a backgroud job say sample_script.sh to foreground (4 Replies)
Discussion started by: rafa_fed2
4 Replies
9. UNIX for Dummies Questions & Answers
Hello Unix Buddies,
cat infinite.sh
#!/bin/sh
while true
do
echo "Infinite loop"
doneI am running it in the background
$ ./infinite.sh > /dev/null &
31634Then i do an exit or click on the cross mark to close the session.
Now my expectation is that when i open up a new... (8 Replies)
Discussion started by: shellscripting
8 Replies
NICE(1) General Commands Manual NICE(1)
NAME
nice, nohup - run a command at low priority (sh only)
SYNOPSIS
nice [ -number ] command [ arguments ]
nohup command [ arguments ]
DESCRIPTION
Nice executes command with low scheduling priority. If the number argument is present, the priority is incremented (higher numbers mean
lower priorities) by that amount up to a limit of 20. The default number is 10.
The super-user may run commands with priority higher than normal by using a negative priority, e.g. `--10'.
Nohup executes command immune to hangup and terminate signals from the controlling terminal. The priority is incremented by 5. Nohup
should be invoked from the shell with `&' in order to prevent it from responding to interrupts by or stealing the input from the next per-
son who logs in on the same terminal.
FILES
nohup.out standard output and standard error file under nohup
SEE ALSO
csh(1), setpriority(2), renice(8)
DIAGNOSTICS
Nice returns the exit status of the subject command.
BUGS
Nice and nohup are particular to sh(1). If you use csh(1), then commands executed with ``&'' are automatically immune to hangup signals
while in the background. There is a builtin command nohup which provides immunity from terminate, but it does not redirect output to
nohup.out.
Nice is built into csh(1) with a slightly different syntax than described here. The form ``nice +10'' nices to positive nice, and ``nice
-10'' can be used by the super-user to give a process more of the processor.
4th Berkeley Distribution May 8, 1986 NICE(1)